store.js VS sql.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)

Hi HN! A friend and I were inspired by projects like https://github.com/sql-js/sql.js and the idea of querying files served over CDN with HTTP range requests. We started thinking: what would a database that was specifically designed for this type of use case look like? So we started building one, and we landed on a functional prototype that we're pretty proud of!

With our prototype, Appendable, we're able to serve and query large (GB+) datasets by hosting them on a static file host like Amazon S3 or Cloudflare R2 without running a separate server and worrying about things like tail latency, replication, and connection pooling -- all that is handled for us by the file hoster.

Additionally, one tenet that we have been following is Appendable won't touch your underlying data, so your jsonl file is preserved and we point at that data instead of consuming it into an Appendable-specific file format. This keeps your data yours and makes it easy to introspect the data: just open it up with your favorite editor aka vim.

We're curious what you think, we're excited to build this out further to get the performance even better and add features like pubsub. Everything is open source at https://github.com/kevmo314/appendable.

Kevin and Matthew

My project is powered by sql.js, I recommend checking that out if you're interested - https://github.com/sql-js/sql.js/

Maybe you can try to use some SQL database compiled as Web Assembly Modules? Like this one for example: https://github.com/sql-js/sql.js

If you want to have persistence, then I would go with a database like Dexie, as it uses IndexedDB and has transactions. If you just want something that's in memory, you could look at Sql.js or something simple like lowdb.

not necessarily. you can host an html/js/sqlite site on github pages for free. json -> sqlite3 js -> sql

Link: https://sql.js.org

Does it work with really large files? Like, >100mb or so. I was considering making something similar but with sqlite.js [1], but the problem with it is that it loads everything in memory, so I wasn't entirely sure how it will deal with larger workloads.

[1]: https://sql.js.org/#/