react/compose-with-tanstack-store

What problem does it solve?

TanStack Table state ownership is difficult when you need sharing, persistence, or fine-grained subscriptions across components and even across multiple tables without wiring many onChange callbacks.

Core Features & Use Cases

• Own one or more table state slices externally (sorting, pagination, rowSelection, columnFilters, columnVisibility, etc.) to remove callback-based state plumbing.
• Share slices across components and tables to enable global filters, coordinated UI state, and consistent behavior across data grids.
• Persist slices outside the table render path (for example, saving column visibility or filters to localStorage).
• Use narrow subscriptions for performance by reading only the atom(s) you care about via selector-based reads.

Quick Start

Ask the AI agent to show how to integrate @tanstack/react-store with useTable by providing a stable sorting atom through options.atoms so the table writes directly to your atom without any onSortingChange handler.