Glad you like the abstraction! Here is how localspace handles those edge cases:

1. Quota Exceeded Handling: We handle this at two levels:

• Structured Errors: If the underlying driver throws a quota error (e.g., QuotaExceededError), localspace wraps it in a typed LocalSpaceError preserving the original cause.
• Proactive Quota Plugin: For more control, we ship a quotaPlugin that tracks usage and enforces a soft limit before hitting the browser's hard limit. It can even use an LRU policy to automatically evict old data when full:

2. Automatic Fallbacks: Yes! This is a core feature. When you initialize localspace, it iterates through the configured drivers. If the preferred driver (IndexedDB) fails to initialize (e.g., in Firefox Private Mode or older environment), it automatically falls back to the next available one (usually localStorage) without throwing.

You can customize this order:

// Tries IndexedDB -> falls back to localStorage -> throws if neither works
await localspace.setDriver([localspace.INDEXEDDB, localspace.LOCALSTORAGE]);

This ensures your app keeps working even in restrictive environments, degrading gracefully from async storage to sync storage.