Getting Started
Vue
@tsworldtech/flux-vue is on the roadmap, not yet shipped. This page will cover wiring Flux's core engine into Vue's reactivity system once it lands.
flux-vue — build log
$ resolving framework target: vue
$ mapping core engine → refs & reactive()
$ scaffolding adapter package
$ checking compatibility across vue 2.7 – 3.x
$ queued alongside angular + svelte adapters
$ status: not yet started
$ resolving framework target: vue
$ mapping core engine → refs & reactive()
$ scaffolding adapter package
$ checking compatibility across vue 2.7 – 3.x
$ queued alongside angular + svelte adapters
$ status: not yet started
Vue is part of a wider push to bring Flux to every major frontend framework — Angular, Svelte, 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 Vue that means binding directly into
ref and reactive() from the Composition API, so a Flux-backed store updates a component the same way any other reactive Vue state would, with no extra glue code in userland.Available today
While flux-vue 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-vue package on the changelog, or watch github.com/tsworldtech/flux for the packages/flux-vue directory to appear.