replistate
v0.1.8
Published
replicate reactive state with local first storage via nostr
Maintainers
Readme
replistate
**simple sync engine that feels like magic**replicate reactive state with local first storage end-to-end encrypted via the NOSTR (web of trust)
async sync engine
"like git ..but for data"Pragmatic simple state synchronization for json data using the familiar mental model of git (or blockchain). State Machine Replication (aka event sourcing or kappa) records fine grained state mutations in a log of events which are send over a shared broadcast messaging medium. Concurrent changes are linearized in a deterministic way to ensure everyone arrives at the same consistent state.
fine grained reactivity
"fine grained reactivity ..but globally"Modern front-end frameworks are arriving at the signals abstraction to organize reactive state dependencies in a way that avoids unnecessary work to re-render the ui. If eg only one json property/field gets edited replistate sends that change event over the wire and directly mutates other apps reactive ui state. The aim is to retain fine grained reactivity globally (across devices, users, app instances). Replistate uses the powerful meta programming abilities of JavaScript for an invisible API that feels like magic
How to use
import { replistate, indexedDB } from "replistate/svelte"
import { generateNsec, nostrNet } from "replistate-nostr"
const repli = replistate({
db: indexedDB(dbName),
net: nostrNet(myNsec) })
repli.addRoom({ url: nostrRelay, nsec: encryptionKey })
const state = $state( [] ) // make state reactive (svelte 5 signal)
const todos = repli(state) // make reactive state "replicatable"
// do some state mutations ...
console.log(todos.version)
console.log(todos.status)
console.log(todos.changes) // git diff
console.log(todos.diffs)
todos.sync() // git commit && git pushFor more details see Demo App (Code)
or read the Tests and design considerations
extensible modules
License
MIT
