themis

Choose based on concrete evidence in the target code path: Svelte or SvelteKit files select Store, React imports and JSX select ReactStore, and Node, server, CLI, or no-UI paths select StreamingStore by default. One app must use exactly one family and never mix them.

Create a Store instance from @augmentcode/themis/svelte-store with your reducer map, call store.init() in the root +layout.svelte with onDestroy(dispose), and start app sagas explicitly via store.runSaga(sagaFn) from onMount. Selectors are called at component init and used as $readables in templates.

No, it uses a custom Redux setup and explicitly forbids Redux Toolkit APIs such as createSlice, configureStore, and createAsyncThunk. Actions and reducers are built with the package's own createAction and createReducer utilities.

Only across separate apps or isolated code paths. A single app, package entry, or code path must not combine Svelte readables, React .useValue() signals, and Kefir observables; mixed repositories route per app based on the files being changed.

Direct selector calls like selectFoo() use Svelte getContext() and only work during component initialization, otherwise throwing lifecycle_outside_component. In handlers, callbacks, or async code, use selectFoo.select(store.state, args) for one-shot reads instead.

All side effects belong in sagas, not components, across every Store family. Components may only contain DOM-local effects such as focus, scroll, and measurement; everything else is dispatched as an action and handled by a saga.