Getting Started
Svelte
@tsworldtech/flux-svelte is on the roadmap, not yet shipped. This page will cover wiring Flux's core engine into Svelte's stores once it lands.
flux-svelte — build log
$ resolving framework target: svelte
$ mapping core engine → stores & runes
$ scaffolding adapter package
$ checking compatibility across svelte 4 – 5
$ queued alongside angular + vue adapters
$ status: not yet started
$ resolving framework target: svelte
$ mapping core engine → stores & runes
$ scaffolding adapter package
$ checking compatibility across svelte 4 – 5
$ queued alongside angular + vue adapters
$ status: not yet started
Svelte is part of a wider push to bring Flux to every major frontend framework — Angular, Vue, and others are on the same track, not an afterthought. The core engine — IDB caching, the offline queue, conflict resolution, sync anchors, multi-tenant scoping — stays exactly the same underneath; what each framework gets is a thin adapter layer that speaks its own idioms. For Svelte that means binding directly into writable stores (and runes on Svelte 5), so a Flux-backed value updates a component through
$store auto-subscription exactly like any other piece of Svelte state, no extra glue code required.Available today
While flux-svelte is in queue, every core Flux capability — the IDB engine, offline queue, conflict handshake, job tracker, sync anchors, and multi-tenant scoping — is already usable from any framework via the framework-agnostic core package, or fully wired up in these:
Track progress on the
flux-svelte package on the changelog, or watch github.com/tsworldtech/flux for the packages/flux-svelte directory to appear.