idb-state-persistence

What problem does it solve?

Web applications must retain state across navigation, reloads, and sessions. Relying on volatile memory or simple localStorage often leads to lost progress and inconsistent UI after refreshes.

Core Features & Use Cases

• StateStore: a generic KV store for single-document state (e.g., user settings, current session).
• Specialized Stores: domain-specific stores with indexes (StoryStore, PracticeProgressStore) for advanced querying.
• State Managers: wrappers that combine StateStore/Specialized Stores with an event system to drive reactive UI updates.
• Data Modeling: use JSDoc typedefs to define data shapes before writing IDB code.
• Integration: IDB is treated as the primary source of truth, guaranteeing local-first persistence across sessions.

Quick Start

Initialize the local-first persistence by wiring up StateStores and a StateManager, then persist an initial state object (e.g., user progress) to the IndexedDB store.