solid/production-readiness

What problem does it solve?

Prevents TanStack Solid Table apps from degrading in real production workloads due to unnecessary bundle size, unstable identities, and overly broad state subscriptions.

Core Features & Use Cases

• Tree-shake features aggressively: Register only the Solid table features you use to reduce state slices and derivations in your bundle.
• Keep critical inputs stable: Ensure _features, columns, and data identities stay stable (with module-scope constants and createMemo where appropriate).
• Use narrow selectors and fine-grained reactivity: Avoid (state) => state patterns and reduce unnecessary re-renders by selecting only the state slices a component needs.
• Pick the right reactivity boundary: Use table.Subscribe only for coarse isolation cases; prefer JSX-level reads for normal updates.
• Scale with external atoms and virtualization: Use per-slice external atoms for server-driven or cross-component state, and pair with @tanstack/solid-virtual for large row counts.

Quick Start

Update your @tanstack/solid-table v9 setup to register only the features you use, keep _features/columns/data stable, and narrow any createTable selectors so components re-render only for the slices they actually render.