solid/production-readiness

Optimize TanStack Table performance in SolidJS by tree-shaking unused table features, keeping `columns` and `data` identities stable, and using narrow state selectors to prevent unnecessary re-renders across large datasets.

Your SolidJS table re-renders unnecessarily due to overly broad state subscriptions. Use narrow state selectors instead of `(state) => state` patterns, and leverage fine-grained Solid reactivity to isolate component updates to only the state slices they render.

The best way to reduce bundle size for a TanStack Solid Table is aggressive `_features` tree-shaking. Register only the specific table features you use, like sorting or filtering, to eliminate unused state slices and derivations from your production bundle.

You can manage server-driven state in TanStack Table using per-slice external atoms. This approach pairs fine-grained Solid reactivity with external atoms to handle cross-component state efficiently without triggering broad component tree re-renders.

You need virtualization for Solid tables with large row counts and frequently updating data. Pairing fine-grained reactivity with `@tanstack/solid-virtual` ensures the table scales effectively by rendering only the visible rows in the viewport.

Use `table.Subscribe` only for coarse isolation cases in SolidJS. For normal state updates, prefer JSX-level reads to maintain fine-grained reactivity boundaries and prevent unnecessary re-render work in your TanStack Table components.