आप स्टेट को कसे persiste आणि hydrate करता?

Question

Accepted Answer

**Persisting** म्हणजे state साठवणे storage मध्ये (localStorage, IndexedDB, backend) जेणेकरून ते पेज रीलोड किंवा सेशनमधून वाचून राहिल; **hydrating** म्हणजे स्टार्टअप वेळी ते अ‍ॅपमध्ये परत लोड करणे. कार्ट, auth tokens, user preferences, आणि draft फॉर्मसाठी सामान्य.

## localStorage सह मूलभूत persist + hydrate

```jsx
function useCart() {
  // HYDRATE: initialize from storage (lazy initializer runs once)
  const [cart, setCart] = useState(() => {
    try {
      const saved = localStorage.getItem("cart");
      return saved ? JSON.parse(saved) : [];      // parse stored JSON
    } catch {
      return [];                                   // guard against corrupt data
    }
  });

// PERSIST: write to storage whenever it changes
  useEffect(() => {
    localStorage.setItem("cart", JSON.stringify(cart));
  }, [cart]);

return [cart, setCart];
}
```

दोन भाग: init वर read-and-parse करणे (hydrate), आणि change वर serialize-and-write करणे (persist).

## Library support

```js
// Zustand persist middleware — automatic persist + hydrate
const useStore = create(persist((set) => ({ ... }), { name: "app-store" }));

// redux-persist for Redux; both handle serialization + rehydration
```

## Storage निवडणे

```text
localStorage  → simple, synchronous, ~5–10MB, strings only (JSON) — preferences, small state
sessionStorage→ like localStorage but cleared when the tab closes
IndexedDB     → large/structured data, async — offline apps, big caches
Cookies       → sent to server; for auth (httpOnly for security)
Backend       → cross-device sync, source of truth for important data
```

## महत्वाचे cautions

```text
⚠️ SSR mismatch: localStorage doesn't exist on the server → guard with typeof window,
   and beware hydration mismatches between server-rendered and client state.
⚠️ Versioning/migration: stored shape may differ from new code → version it and migrate.
⚠️ Don't persist sensitive data (tokens) in localStorage (XSS-readable) — prefer httpOnly cookies.
⚠️ Don't persist server state you can refetch (let React Query handle caching).
⚠️ Validate/guard on hydrate — stored data can be stale or corrupt.
```

## हे का महत्वाचे आहे

Persistence खरे UX मूल्य वितरीत करते — कार्ट रीलोड्स वाचून राहते, preferences आणि drafts हरले जात नाहीत, users लॉग इन राहतात.

पण naive implementation सूक्ष्म, गंभीर समस्या सादर करते: SSR hydration mismatches, stale/corrupt data, schema-migration breakage, आणि **security risks** (tokens साठवणे XSS-readable storage मध्ये).

Persist/hydrate pattern जाणून घेणे, data साठी योग्य storage निवडणे, आणि cautions चे पालन करणे (SSR साठी guard, schema version, secrets असुरक्षितपणे साठवू नका, refetchable server state persist करू नका) हे आहे जे persistence robust बनवते hard-to-diagnose bugs चा स्रोत न राहता.