store.js VS Dexie.js

it's not made up, feel free to look it up. In older versions if the site was in a private window, writing something to localStorage would throw an exception. Was a pain in the ass and caused a lot of bugs. https://developer.apple.com/forums/thread/71593 https://news.ycombinator.com/item?id=17231508 https://github.com/marcuswestin/store.js/issues/42

Some javascript libraries require you to configure them using webpack. For example, https://github.com/marcuswestin/store.js/ , if you want to use sessionstorage only without anything else. You need to rebuild the library using webpack. If you can tinker with building libraries and providing custom builds that suit your need and load them into importmap, then it is better to use importmap.

I'm using store package to persist data after page reload.

store is basically a localStorage wrapper. If you want your data to persist even if on page reload, you might consider using it.

I've been using store, it's basically a localStorage wrapper.

and the pokemon user can catch is saved using session based local storage, Store js (https://github.com/marcuswestin/store.js)

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.