dexie-cache-sync

You can sync Convex data to IndexedDB by mapping it to a Dexie cache with orphan detection and cascade deletes. This local-first sync layer reduces latency, enables offline capabilities, and provides real-time UI updates through Dexie liveQuery.

Optimistic updates are kept in React state only, while the Dexie cache holds authoritative data. This separation enables fast UI responses without risking cache inconsistency during Convex data synchronization.

Yes, the Dexie caching layer includes an SSR guard that prevents IndexedDB usage on the server. This ensures safe server-side rendering in browser environments while maintaining offline-first capabilities for client-side Convex data synchronization.

The Dexie caching layer handles cascade deletes by automatically removing related data like attachments, toolCalls, and sources when a parent message is deleted. This ensures safe multi-table reconciliation during local-first Convex data synchronization.

Orphaned records occur when related data loses its parent reference during synchronization. The Dexie caching layer includes orphan detection to identify and clean up these records during multi-table reconciliation with Convex data.

Yes, you need to initialize a Dexie schema consistent with the required tables, including conversations, messages, notes, tasks, projects, attachments, toolCalls, sources, pendingMutations, and userPreferences to wire up Convex data syncing properly.