localForage VS Dexie.js

Not really an answer but have you looked into https://github.com/localForage/localForage

I may not be pointing you in the right direction but, please read about [IndexDB storage](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB\_API) method and packages like [localForage](https://localforage.github.io/localForage/) that use it under the hood.

LocalForage: this is a wrapper around IndexedDB, WebSQL, LocalStorage, and SessionStorage with a way to define more interfaces (called drivers) *for additional storage solutions. It does a great job handling all your serialization needs, it is **asynchronous **and handles a large set of data types. Its **API resembles Web Storage API* and it is ridiculously simple to learn.

Depending on what kind of storage requirements you have, LocalForage might be a good fit. It provides a unified API to access WebSQL, indexedDB or localStorage.

I find localForage is pretty helpful for this stuff https://github.com/localForage/localForage

localForage (https://localforage.github.io/localForage/) mirrors localStorage syntax, but uses IndexedDB in the background. If that's not supported, it uses WebSQL and then LocalStorage

This is why we have localForage.

The word on the street is that https://github.com/rhashimoto/wa-sqlite is nearly production ready, closing in on the neat 1.0.0 release, with its IDBBatchAtomic engine highly recommended at https://www.powersync.com/blog/sqlite-persistence-on-the-web. You can try out the benchmark https://rhashimoto.github.io/wa-sqlite/demo/benchmarks.html.

And the other contestant is Dexie, stable https://dexie.org/.

If you were to branch into a new venture today, which one would you pick? And why?

That said, there are some great ways to wrap IndexedDB to make it easier to work with. Since I’m writing this article I’ll toss in my local-first framework Verdant, which can be used without the sync features as a standalone IndexedDB-powered database with a type-safe schema and deployable data migrations. For a lighter-weight approach, maybe check out Dexie.

Using IndexedDB. I have heard its pretty cumbersome to use. There are wrappers like Dexie.js but I am not sure if it works seamlessly with Tauri or if it is the correct thing for my use case.

I use IndexedDB, specifically the idb library (https://github.com/jakearchibald/idb), or Dexie.js (https://dexie.org/) if you are more novice. This works great for large sets of data. For smaller amounts, Chrome Storage API will do.

To make things easier, Dexie.js provides a straightforward and simplified process of creating databases, storing data, updating data and database migrations, etc., over the top of indexedDB.

If you are just looking for a solution for your IndexedDB needs I find Dexie to be one of the best but depending on other needs, the others in the list are also good to consider.