ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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
Configuration goal I have a Zustand store using the persist middleware (default localStorage via createJSONStorage ) with version: 1 . The state shape is changing: a nested preferences object is gaining new fields with defaults, and one old field is being renamed. I need existing users' persisted snapshots to keep working after the update. Constraints and un
Persisted Zustand state not available on initial mount This question concerns Zustand's persist middleware and whether rehydrated state is available before the first component render. The goal is to diagnose whether recovered data from localStorage is guaranteed to exist when a selector-based component mounts, or whether the component always renders with the
zustand
react