new-store

A shared frontend store coordinates state across multiple components, pages, and hooks, removing the need for ad-hoc prop drilling or duplicate local state. It uses a generic createStore pattern with hydrate, set, and reset APIs.

Shared store implementations use narrow selector hooks that ensure components only re-render when the specific selected state slice changes. This prevents unnecessary re-renders across unrelated components sharing the same store.

Yes, the shared store includes auth-aware lifecycle management to automatically hydrate state on login and reset it on logout. This ensures user-specific state is cleared properly during authentication transitions.

Using a centralized store with a generic createStore pattern is an effective way to manage cross-page state. It supports portal-local or shared placement and offers domain-specific verbs for targeted state mutations.

Store hydration is needed during the lifecycle management phase when a user logs in. It initializes and populates the shared store with necessary data so multiple components have immediate access to the required state.

Yes, the createStore pattern supports domain-specific verbs for mutations alongside the standard hydrate, set, and reset APIs. This allows you to define custom actions tailored to your specific state update requirements.