Getting Started
Angular
@tsworldtech/flux-angular is on the roadmap, not yet shipped. This page will cover the Signals adapter for Angular 16+ and the plain service pattern for Angular 14–15 once it lands.
flux-angular — build log
$ resolving framework target: angular
$ mapping core engine → reactivity primitives
$ scaffolding adapter package
$ checking compatibility across ng 14–17
$ queued alongside vue + svelte adapters
$ status: not yet started
$ resolving framework target: angular
$ mapping core engine → reactivity primitives
$ scaffolding adapter package
$ checking compatibility across ng 14–17
$ queued alongside vue + svelte adapters
$ status: not yet started
Angular is one part of a wider push to bring Flux to every major frontend framework — Vue, 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 Angular that means a native
Signals adapter for modern versions and a plain injectable service pattern for older ones, so the integration feels native to Angular rather than bolted on.Available today
While flux-angular 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-angular package on the changelog, or watch github.com/tsworldtech/flux for the packages/flux-angular directory to appear.