solid/client-to-server

What problem does it solve?

You need to render a TanStack Solid table when the server owns sorting, filtering, and pagination, but you still want to keep the same table APIs and UI behavior in the browser.

Core Features & Use Cases

• Manual row-model ownership: Use manualPagination, manualSorting, and manualFiltering (and related manual* flags) so the client doesn’t recompute those slices.
• Lifted server state with Solid signals/atoms: Store and subscribe to pagination/sorting/filter state using Solid signals or @tanstack/solid-store atoms (via createAtom + useSelector).
• Correct server totals: Provide rowCount so pagination controls like getPageCount() and page navigation reflect server-side totals.
• Pair with a fetcher: Commonly combine with a query/fetch layer (e.g., TanStack Query) by keying requests on the lifted state.

Quick Start

Tell your AI agent to convert your existing @tanstack/solid-table client setup into a server-driven version by lifting pagination/sorting/filter state into Solid atoms or signals, setting the corresponding manual* options, supplying rowCount from the API response, and removing the matching client row-model factories for those slices.