ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #zustand
Learn how Zustand's shallow equality helper stops wasteful re-renders, when to use custom equality functions, and how to verify the impact with React DevTools.
A diagnostic guide for Zustand v4.x covering stale selectors, hydration mismatches, Immer misuse, TypeScript inference, testing isolation, and subscribe pitfalls — with cause tables, ordered checks, and fixes tied to findings.
Zustand's persist middleware stores a frozen snapshot of your state in users' browsers. Use versioned migrations, partialize, and storage guards to evolve that state safely across releases.
Learn why Zustand subscribers may miss updates and how to diagnose middleware, mutation, closure, and subscription issues with step‑by‑step checks and fixes.
Persist Zustand state across reloads with minimal design: a single store, short key, versioning, and safety checks. Learn how to validate storage, handle failures, and change the architecture when SSR, cross‑tab sync, or sensitive data arise.
A decision guide comparing localStorage, sessionStorage, and custom storage for Zustand persist middleware, with trade-offs and a working configuration you can validate today.
Zustand's persist middleware handles localStorage hydration automatically, but production use requires deliberate choices: whitelist serializable state with partialize, gate renders during SSR with onRehydrateStorage, and verify with memoryStorage in tests. Here's the practical guide.
Avoid unnecessary React re-renders in Zustand by using atomic selectors with strict equality, encapsulating actions in the store, and accessing state outside components via getState().
Learn how Zustand’s selector feature lets React components subscribe only to the data they need, reducing re‑renders and keeping state logic simple. A worked example shows the performance difference and highlights common pitfalls.
react
typescript