π Say hello to @atomico/hooks@4, Improvements for better maintenance.
Maintenance improvement
starting from version 4, @atomico/hooks will be managed as a monorepo. This is done with the aim of:
- Improving the consumption of these hooks, allowing developers to select the version of the hook to use in their project.
- Including new hooks more quickly, as they won't break the usage of the @atomico/hooks package by default. Developers can roll back or update on a per-hook basis rather than for all hooks.
This version breaks some hooks from version 3, such as:
Removed Hooks
- use-async-effect: Prefer using Atomico's asynchronous API.
- use-channel: Prefer the core of Atomico, which already has APIs for working with contexts.
- use-child-nodes: Prefer the useSlot hook, as use-child-node is inaccurate if multiple renders occur on the same web component.
- use-controller: Prefer Atomico's hooks API (can be reintegrated upon community request; feel free to request it via issue).
- use-css: Prefer Atomico's core API for handling CSS.
- use-dollars: Prefer the approach of using slots as templates.
- use-queue-task: Unused (can be reintegrated upon community request; feel free to request it via issue).
- use-unique-id-selector: Prefer useId from the core of Atomico.
- use-script: Prefer using Atomico's asynchronous API.
Renamed Hooks
- use-history = use-value-history: Facilitates understanding of cumulative values between renders.
Message from the author @UpperCod
We'll be attentive to your experience with this new version of Atomico and @atomico/hooks. If you have any feedback or questions, feel free to share them. Happy coding!