TanStack Table V9 Beta Released with Tree-Shakable Features and Reworked State Management

TanStack Table V9 Beta Announced

TanStack Table, a headless UI library for building tables and datagrids across JavaScript frameworks, has announced the beta release of TanStack Table V9. This foundational update reworks state management, memory usage, bundle size, and extensibility while retaining the core table logic.

The V9 beta, announced on June 8, 2026, ships with state management built on TanStack Store, fine-grained re-render control through state subscriptions, and lower memory usage at scale. It also includes tree-shakable features with type safety, a clearer plugin model, and rewritten devtools. The library supports React, Preact, Angular, Solid, Vue, Svelte, and Lit.

Opt-in Features and State Management Changes

A significant change in V9 is that features are now opt-in. Unlike V8, where all features shipped together, V9 registers only the features a table uses. This allows small tables to start at approximately 5kb, with additional features like sorting, filtering, and pagination pulled in as needed for larger enterprise grids. TypeScript enforces this, ensuring APIs like setSorting only exist if their corresponding feature is registered.

State management has also been overhauled. The migration guide indicates that useReactTable is now useTable, and state flows through table.state, table.store, and per-slice atoms instead of getState(). A new table.Subscribe allows specific UI elements, such as row selection counts, to re-render independently without affecting the entire table instance. Lead maintainer Kevin Van Cott stated that this design was adapted from TanStack Form and Store, and the stabilization of the React Compiler necessitated the rewrite due to V8's patterns breaking under it.

Development Challenges and Community Feedback

Kevin Van Cott acknowledged the multi-year delay in the release, admitting it "has probably taken too long" and that attempting to address every V8 complaint simultaneously was "a big mistake." Ahmad Fiaz, writing on Medium, cautioned that the new atoms API in V9 beta is not a direct replacement for controlled state, a distinction relevant for both Angular and React applications.

The extensibility improvements address a recurring complaint from developers, who previously described difficulties in extending the library for growing projects. However, initial community feedback, such as a Reddit thread comment from Arceus919, indicates that some users still perceive a gap in per-table state management, noting that "everything is still global" rather than per-table.