svelte/compose-with-tanstack-store

Wire TanStack Table v9 state into Svelte reactivity by using table.atoms.<slice> and table.store with subscribeTable to ensure sorting, pagination, and filtering updates trigger reactive UI changes correctly.

The difference between table.atoms.<slice> and table.state.<slice> is reactivity: atoms provide reactive subscription surfaces for Svelte runes, while state is a static read surface that does not trigger UI updates on its own.

Mixing table.atoms with table.state causes reactivity issues because state.<slice> bypasses atom subscriptions, preventing Svelte runes from detecting sorting or pagination updates and leading to stale UI rendering.

Yes, you can use createAtom to externally own and manage TanStack Table pagination slices in Svelte, ensuring stable atom creation and proper precedence rules when projecting table state through createTable selectors.

Subscribe to table.atoms.pagination using subscribeTable in your Svelte component to isolate reactive updates, ensuring only pageSize changes trigger UI re-renders while ignoring unrelated table state mutations.

Yes, TanStack Table v9 works with Svelte 5 runes for row selection and filtering by mapping table.atoms and table.store to runes via useSelector and subscribeTable, enabling proper selector projections and reactive state composition.