svelte/table-state

To manage TanStack Table v9 state in Svelte 5 using runes, wire `createTable` with selector support and integrate `$state`, `$derived.by`, and `$effect.pre` to sync table state with the DOM before rendering for predictable reactive updates.

Preventing stale renders in a Svelte 5 datagrid requires fine-grained subscriptions using `subscribeTable(atom, selector?)` with `.current`, limiting rerenders to specific UI parts that need updates via slice-safe state selection.

Access specific state slices in a TanStack Table v9 Svelte adapter by reading `table.state` via selectors and using `table.atoms` or `table.baseAtoms`, ensuring you respect which features are registered in your table configuration.

Yes, you can use external atoms via `@tanstack/svelte-store` for controlled state ownership in Svelte 5 table state, or choose between `initialState` and `state` plus `on[State]Change` callbacks for managing controlled state slices.

Svelte 5 table UI updates inefficiently when lacking fine-grained subscriptions; applying `subscribeTable` with shallow selection semantics ensures only the UI components depending on changed atoms rerender, optimizing reactive performance.