Engine portability

The same filter state, in all 6 stacks

Every vertical reads its state from the same ?f parameter, through a serializer whose decode detects its own format tag. A link built here opens in any of them — React, Vue, Svelte, Angular, or no framework at all — and reproduces the identical result set.

• React RTK React 19

  Adds the optional Redux mirror via redux-bridge — the engine stays the source of truth.

  @filter-enginez/react-signals signals

• React plain React 19

  The same app with no store library at all, proving the Redux mirror is optional.

  @filter-enginez/react-signals signals

• SvelteKit SvelteKit 5

  Runs the isomorphic core in SvelteKit’s own server tier, with a zero-JS SSR fallback.

  @filter-enginez/svelte-signals signals

• Vue Vue 3

  Holds the engine in shallowRef — Vue’s deep proxy would break its signals.

  @filter-enginez/vue-signals signals

• Angular Angular 22

  Zoneless and standalone; consumes the engine’s Observables natively, so the binding is DI only.

  @filter-enginez/angular-rxjs rxjs

• Vanilla None

  /books goes through reactive-signals, /books-raw through the bare core — the pair shows what the adapter buys.

  no binding — bare core none

Links are full navigations by design: four of the six hydrate ?f only at mount, so a client-side transition would leave their engines untouched. Back to the dataset hub