TanStack Table core
TanStack Table coordinates state and row processing. The renderer owns markup, styles, semantics, and interaction accessibility. Use the installed framework adapter in UI code; use constructTable for framework-neutral integrations.
Minimal setup
import {
constructTable,
createColumnHelper,
tableFeatures,
} from '@tanstack/table-core'
import { storeReactivityBindings } from '@tanstack/table-core/store-reactivity-bindings'
type Person = { id: string; name: string }
const features = tableFeatures({
coreReactivityFeature: storeReactivityBindings(),
})
const helper = createColumnHelper<typeof features, Person>()
const columns = helper.columns([helper.accessor('name', { header: 'Name' })])
const data: Person[] = [{ id: '1', name: 'Ada' }]
const table = constructTable({
features,
columns,
data,
getRowId: (row) => row.id,
})
for (const row of table.getRowModel().rows) {
console.log(row.getAllCells().map((cell) => cell.getValue()))
}
Essential constraints
- The core row model is automatic. Optional APIs and state exist only after their feature is registered.
- Keep
features, data, and columns stable between meaningful changes. Derive changing arrays with the adapter's memo/computed mechanism; an inline .map(), .filter(), column factory, or fresh [] fallback invalidates model work and can cause render loops.
- Let
createColumnHelper and helper.columns() preserve accessor value types. Derive feature types from the concrete registry when an explicit boundary is needed.
- Call row, cell, column, and header methods on their instance. Use
row.getValue('name') or a callback that calls it; extracting const { getValue } = row loses its this receiver.
- Render the final
table.getRowModel().rows. The table object itself is not a DOM component.
Read for the current task
| Task |
Read |
| Add or repair optional features, processing slots, or prerequisites |
Feature architecture, then its relevant feature reference |
| Choose state ownership, initialize or reset state |
Shared state |
Fix ColumnDef inference, reusable options, or scoped meta |
TypeScript inference |
| Diagnose a missing export, option, state slice, or instance method |
API discovery |
| Implement row numbers, identity, or display-index behavior |
Rows |
| Author behavior beyond built-ins or typed meta |
Custom features |
| Migrate an existing v8 table |
Migration audit |
For framework construction and rendering, load the installed package's getting-started skill with intent load <package>#getting-started, replacing <package> with the actual adapter package, such as @tanstack/react-table. For reactive reads or controlled wiring, load that package's table-state skill directly.
Installed API discovery
Start at node_modules/@tanstack/table-core/dist/index.d.ts and follow exported declarations. Adapter declaration layouts and missing-API diagnosis are in API discovery; read it when the expected export or declaration path is absent.
1---2name: core3description:4 Use TanStack Table v9 core architecture, stable data and columns, and inferred5 types. Route setup, missing APIs, row models, state, features, and framework-specific work.6metadata:7 source: https://skillmd.com/skills/tanstack/core8 type: core9 library: '@tanstack/table-core'10 library_version: '9.3.1'11sources:12 - TanStack/table:docs/overview.md13 - TanStack/table:docs/guide/tables.md14 - TanStack/table:docs/guide/data.md15 - TanStack/table:packages/table-core/src/index.ts16 - TanStack/table:docs/guide/helpers.md17 - TanStack/table:docs/guide/column-defs.md18 - TanStack/table:docs/guide/table-and-column-meta.md19 - TanStack/table:packages/table-core/src/helpers20 - TanStack/table:packages/table-core/src/types/TableFeatures.ts21 - TanStack/table:docs/framework/react/guide/migrating.md22 - TanStack/table:docs/guide/rows.md23 - TanStack/table:packages/table-core/src/core/rows/coreRowsFeature.utils.ts24---2526# TanStack Table core2728TanStack Table coordinates state and row processing. The renderer owns markup, styles, semantics, and interaction accessibility. Use the installed framework adapter in UI code; use `constructTable` for framework-neutral integrations.2930## Minimal setup3132<!-- skill-snippet:check -->3334```ts35import {36 constructTable,37 createColumnHelper,38 tableFeatures,39} from '@tanstack/table-core'40import { storeReactivityBindings } from '@tanstack/table-core/store-reactivity-bindings'4142type Person = { id: string; name: string }43const features = tableFeatures({44 coreReactivityFeature: storeReactivityBindings(),45})46const helper = createColumnHelper<typeof features, Person>()47const columns = helper.columns([helper.accessor('name', { header: 'Name' })])48const data: Person[] = [{ id: '1', name: 'Ada' }]49const table = constructTable({50 features,51 columns,52 data,53 getRowId: (row) => row.id,54})5556for (const row of table.getRowModel().rows) {57 console.log(row.getAllCells().map((cell) => cell.getValue()))58}59```6061## Essential constraints6263- The core row model is automatic. Optional APIs and state exist only after their feature is registered.64- Keep `features`, `data`, and `columns` stable between meaningful changes. Derive changing arrays with the adapter's memo/computed mechanism; an inline `.map()`, `.filter()`, column factory, or fresh `[]` fallback invalidates model work and can cause render loops.65- Let `createColumnHelper` and `helper.columns()` preserve accessor value types. Derive feature types from the concrete registry when an explicit boundary is needed.66- Call row, cell, column, and header methods on their instance. Use `row.getValue('name')` or a callback that calls it; extracting `const { getValue } = row` loses its `this` receiver.67- Render the final `table.getRowModel().rows`. The table object itself is not a DOM component.6869## Read for the current task7071| Task | Read |72| ------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |73| Add or repair optional features, processing slots, or prerequisites | [Feature architecture](../table-features/SKILL.md), then its relevant feature reference |74| Choose state ownership, initialize or reset state | [Shared state](../table-state/SKILL.md) |75| Fix `ColumnDef` inference, reusable options, or scoped meta | [TypeScript inference](references/typescript.md) |76| Diagnose a missing export, option, state slice, or instance method | [API discovery](references/api-not-found.md) |77| Implement row numbers, identity, or display-index behavior | [Rows](references/rows.md) |78| Author behavior beyond built-ins or typed meta | [Custom features](../custom-features/SKILL.md) |79| Migrate an existing v8 table | [Migration audit](../migrate-v8-to-v9/SKILL.md) |8081For framework construction and rendering, load the installed package's `getting-started` skill with `intent load <package>#getting-started`, replacing `<package>` with the actual adapter package, such as `@tanstack/react-table`. For reactive reads or controlled wiring, load that package's `table-state` skill directly.8283## Installed API discovery8485Start at `node_modules/@tanstack/table-core/dist/index.d.ts` and follow exported declarations. Adapter declaration layouts and missing-API diagnosis are in [API discovery](references/api-not-found.md); read it when the expected export or declaration path is absent.