Releases: hmans/statery
Releases · hmans/statery
v0.7.1
v0.7.0
Minor Changes
- 8928b16: Statery's React hooks now internally use React 18's new
useSyncExternalStore
hook. This simplifies the library implementation and makes sure that store updates don't cause UI drift. (Thanks @smartinio!) - 8c555e2: This package is now built using TypeScript 5.1.
v0.6.3
Patch Changes
- a9923df: Fixed: The library recently started using
useLayoutEffect
instead ofuseEffect
, breaking it in SSR environments, where usage of that hook throws errors. This has been fixed. (Thanks @daveschumaker!)
v0.6.2
v0.6.1
v0.6.0
Minor Changes
- d2eb9b4: Fixed:
useStore
now hooks into the store usinguseLayoutEffect
, notuseEffect
- 53fff47: Refreshed all of the package's dependencies and brushed up its test setup.
- 5b64a96: Switched the library's build tool to Preconstruct. If everything breaks, it's on me! 🎉
- 53fff47: Statery now requires React 18 and up!
- 75d0a40: Simplify types.
- da27eba:
set
now takes a second options argument. The only available option so far isforceNotify
; when set to true, all updated properties will be notified, regardless of referential equality to the previous value.
Patch Changes
- a5f5533:
useStore
will now force the component to re-render if a change was detected between the React render/reconcile stage and the invocation of the layout effect that actually sets up the subscription listener. This improves reactivity in situations where values were changed in the store during the render phase, or imperatively from outside of your React component tree.
v0.6.0-next.3
Minor Changes
- 5b64a96: Switched the library's build tool to Preconstruct. If everything breaks, it's on me! 🎉
v0.6.0-next.2
Patch Changes
- a5f5533:
useStore
will now force the component to re-render if a change was detected between the React render/reconcile stage and the invocation of the layout effect that actually sets up the subscription listener. This improves reactivity in situations where values were changed in the store during the render phase, or imperatively from outside of your React component tree.