add-scoped-store

Per-entity scoped Zustand stores isolate state across independent entities like tabs or workspaces by creating isolated store instances per scope ID, preventing state leakage between contexts without relying on global singletons.

You can manage isolated Zustand stores using the createScopedStore API to initialize per-scope stores, then call getOrCreate with a scope ID to obtain or create the specific store instance for that entity.

Yes, scoped Zustand stores work outside React components by using the getOrCreate function with a scope ID to access isolated state instances, while useScoped is used specifically within React component trees.

To prevent memory leaks with per-entity state management, use the built-in cleanup behavior to remove unused scopes and their associated store instances when entities are no longer active or needed.

The best way to handle per-tab state is defining per-entity scoped Zustand stores with TypeScript types, using useScoped within components and getOrCreate in non-React code to manage isolated state per tab ID.

Yes, TypeScript types are required to implement scoped stores, as the createScopedStore API relies on TypeScript to initialize per-scope stores and dynamically patch actions across entities and lifecycles.