Is it persisted?

[jswhisperer]

I maybe wrongly assume it's persisted temporily with an Browser Storage API / filesystem on server?

If so will there be options to set persistence modes like
https://signaldb.js.org/data-persistence/

[Akryum]

rstore core doesn't implement offline access (or any data access really), but it can be implemented in the plugins. See #15

[jswhisperer]

No worries thanks for answering, looks like a great library.

I might highlight at least to me this blurb on the homepage is a bit misleading?

Local-first Cache Cache reads are computed on the client, enabling offline and realtime apps.

Does it technically enable offline apps that much? To me at least it kinda reads like there might be a service worker or browser storage.

[Akryum]

It being local-first does enable having offline features in the app. Official builtin offline is being worked on but you can also implement it yourself too. :)

[jswhisperer]

The plugin route is totally a good design decision 🎉

I'm sure the community will jump on it soon, I guess though one possible future challenge might be, sever store (in-memory, fs, etc) vs client store (localStorage, indexDB, turso , etc)... as in do they sync two way binding, and what is the transpofrt method for realtime updates, or is one the source of truth etc.

[andyjamesn]

Is adding support for PGglite in any plans? this would also have an added benefit of making it persistant?

[Akryum]

An official offline plugin is here: https://rstore.dev/guide/data/offline.html
Of course you can still create your own offline solution :)