ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #zustand
A client-side draft-autosave store built with zustand's persist middleware (assuming the current 5.x line, with 4.x behaving the same) has to survive a page reload. Part of its state is not JSON-native: a last-edited Date , a Set of selected ids, and a Map used as a keyed cache. The middleware's default storage path serializes through JSON.stringify and pars
When using Zustand's persist middleware in a server‑side rendered application, the store throws a ReferenceError: window is not defined because localStorage is unavailable during SSR. Developers currently work around this by conditionally initializing the middleware or providing a custom storage object. The library does not yet ship an automatic in‑memory fa
Goal Measure whether a component re-rendering on every store update is caused by an unstable selector reference, a missing shallow equality function, or genuinely changing state — before applying any optimization. Constraints and uncertainty The subscribeWithSelector middleware exposes store.subscribe(selector, listener, options) for slice-based subscription
Goal is to define the exact moment persisted state becomes authoritative in a Zustand store that uses the persist middleware during server-side rendering. The store is created outside the React component lifecycle and persist synchronizes state to a storage engine. Hydration is the restoration of persisted state from storage into the store on application ini
Zustand's persist middleware rehydrates the store from persisted JSON and optionally runs a migrate function that converts outdated state shape to the current TypeScript type, using a version option supplied in the persist configuration. The migration runs only during initial load, not on subsequent state updates, and Zustand does not automatically roll back
This question investigates the defined execution order when multiple set operations are issued concurrently within a Zustand store, particularly when async middleware such as persist is active. The goal is to clarify whether call sequencing is deterministic, and how shallow merge semantics interact with interleaved asynchronous side effects. Relevant constra
Zustand Selector Equality for Nested State Updates The goal is to configure a Zustand store so React components select nested objects from state without unnecessary re-renders. The default useStore comparison uses Object.is , and zustand/shallow compares only top-level properties of the selected value. Components should re-render only when a deeply nested le
Zustand's subscribe function allows for transient state updates by listening to changes outside the React render cycle. When using a selector to isolate specific state slices, the callback is triggered based on the result of that selector. There is uncertainty regarding how the subscription mechanism handles selectors that return new object references or com
When an async action in a Zustand store retries on failure, multiple setState calls can be issued in quick succession. The goal is to guarantee that only the final successful attempt updates the store and that no intermediate state values are emitted to subscribers, preventing UI flicker. Constraints include avoiding duplicate writes, handling concurrent ret
react