solid/compose-with-tanstack-store

To share TanStack Solid Table state across components, provide external TanStack Store atoms in the `atoms` option during `createTable`, establishing a single source of truth for slices like pagination or sorting that multiple components can coordinate on.

The atom-wins rule dictates that when you provide an external TanStack Store atom for a specific state slice, that atom takes precedence over any `state` and `on*Change` props configured for the same slice, ensuring predictable external ownership and reactive reads.

You can read reactive table state slices in Solid without over-subscribing by using `useSelector` with optional `shallow` compare for isolated rendering boundaries, or by using `table.state()` for Solid-idiomatic selector reads within tracked scopes.

Yes, you can use TanStack Store to drive Solid Table pagination from URL or server updates by assigning external atoms to the pagination slice, allowing cross-component synchronization and external updates to flow predictably into the table state.

When using atoms, you can access TanStack Solid Table state through three Solid-friendly surfaces: `table.atoms.<slice>.get()` for fine-grained reactive reads, `table.store` for snapshot-style access, and `table.state()` for selector reads.