Track TanStack Table v9 compatibility for Data Grid

[CarlosZiegler]

Context

TanStack Table v9 has been released as latest for @tanstack/react-table (9.0.0). ReUI Data Grid currently targets the v8 API surface.

Relevant files inspected on main (c2f1dce):

• package.json uses @tanstack/react-table: ^8.21.3
• packages/registry/bases/base/components/data-grid/package.json uses ^8.21.3
• packages/registry/bases/radix/components/data-grid/package.json uses ^8.21.3
• content/docs/(components)/base/data-grid.mdx documents a React Compiler workaround specifically for TanStack Table v8 ("use no memo" around useReactTable)
• registry-reui/bases/*/reui/data-grid/** imports v8 types/functions (Table<TData>, Column<TData>, flexRender, table.getState(), setColumnSizingInfo, column.pin("left"/"right"), etc.)
• generated/public registry JSON currently lists @tanstack/react-table as an unversioned dependency in multiple Data Grid items

Why this matters

New shadcn registry installs can resolve unversioned @tanstack/react-table to v9, while ReUI's Data Grid source and examples still use v8 APIs. A full v9 migration is larger than a simple version bump:

• useReactTable becomes useTable({ features, ... })
• row models move into tableFeatures() slots
• ColumnDef, Column, Table, Row, Cell, etc. get feature generics
• pinning changes from physical left/right to logical start/end
• columnSizingInfo becomes columnResizing
• sorting/function registry names change (sortingFn/sortingFns -> sortFn/sortFns)
• v8 React Compiler workaround docs likely need to be revisited once v9 is supported

Suggested path

Short-term compatibility fix:

• Pin all registry dependencies for Data Grid and Filters entries to the supported v8 range, e.g. @tanstack/react-table@^8.21.3, so new installs do not accidentally pull v9.
• Optionally add a docs note that Data Grid currently targets TanStack Table v8 until a v9-native migration lands.

Long-term migration:

• Introduce explicit tableFeatures() definitions for the Data Grid feature set.
• Replace v8-only APIs and type signatures across base/radix primitives and examples.
• Rework pinning and sizing/resizing logic (left/right -> start/end, columnSizingInfo -> columnResizing).
• Verify Data Grid examples covering sorting, filtering, pagination, selection, visibility, column resizing, pinning, row pinning, virtualization, DnD, infinite scroll, and tree rows.

I searched for existing issues mentioning TanStack Table v9 and did not find a duplicate.

[focus0802]

Update: PR #116 is no longer a draft and now covers the related TanStack Table v9 DataGrid reactivity defects.

• Committed column-sizing changes now reach the table CSS variables without subscribing the whole grid to every active-resize tick.
• Row renderers receive data through a separate reactive context, so edits refresh even when row count and row IDs stay the same.
• Regular and DnD tables use bounded in-table skeleton rows for initial and background loading; the virtual table keeps its empty-initial spinner because there are no rows to skeletonize.
• Ordinary, column-DnD, row-DnD, and virtual paths are covered, with Base UI and Radix registry artifacts regenerated.

The common cause is the ReUI DataGrid adapter's memo/context boundary around TanStack Table v9 state, rather than a TanStack Table core defect. Local verification covers 2,896 registry items with zero Base/Radix mismatches, a 192/192-page production build, and 56 focused regression tests in the consuming Leilei app. The current Vercel check failures are authorization gates, not build failures.

#111 should remain open for the broader v9 compatibility items that are not covered by this PR.