Ariakit is now stable. If you have been waiting to integrate Ariakit into your project, I can finally recommend it for production use.
I’m delighted to announce that the ariakit npm package is now stable (What is Ariakit?). If you’ve been eagerly awaiting the ideal opportunity to integrate Ariakit into your project, I can finally recommend it for production use. It’s already been successfully used by amazing projects such as WordPress, Todoist, Guide, Croct, and many others.
This means that Ariakit now follows semantic versioning and will introduce fewer breaking changes. Whenever feasible, these changes will be preceded by soft deprecations, followed by deprecation warnings before the actual breaking change occurs.
Ariakit is antifragile
Over the past year, numerous bugs have been reported, and all of them could be resolved in userland before a fix was implemented in the library. By inspecting the closed bugs in the repository, you will notice that each of them is labeled with “has workaround”.
This means that you don’t have to wait for a general solution to be proposed, discussed, implemented, tested, reviewed, merged, and published to npm in order to address your specific issue and move forward, delivering amazing features to your clients.
As both a maintainer and consumer of the project, I’m pleased that I can quickly fix any bug I encounter while using Ariakit in my apps without having to go through the entire process of figuring out a suitable solution. This not only saves time but also contributes to finding the proper fix.
When we address a bug report or feature request in the project, we create an example accessible in the browser and make sure it’s automatically tested on every commit to the library. This approach ensures that we don’t introduce any regressions in the future.
This isn’t an official announcement yet
The library is still being released as v0.x.x. This is because I intend to synchronize an official release with the launch of the ariakit.org website. Stay tuned!