Audit and migrate Table v8 to v9. Inventory affected APIs, follow the shared checklist, and read only the required architecture, state, feature, and TypeScript mappings.
Read core first. Audit every item below before choosing detailed mappings. This shared checklist owns the complete core migration; the installed adapter's migration skill owns construction, rendering, framework requirements, and reactive wiring.
Procedure
Establish passing tests for the existing table and inventory its enabled interactions, imports, options, and state owners.
Follow the whole audit checklist. Read a mapping reference when the audit finds affected code; preserve behavior while migrating features and construction.
Load the installed adapter with intent load <package>#migrate-v8-to-v9 and its table-state skill. Substitute the actual adapter package. React, Preact, Solid, Svelte, Vue, Angular, and Lit have migration skills; Alpine, Ember, and Octane have no v8 adapter migration journey.
Type-check, exercise every enabled interaction and client/server stage, and complete the explicit v9 setup.
Treat useLegacyTable as a deprecated React-only bridge for an existing incremental migration. It bundles every feature, can exceed the v8 bundle, and is not the target architecture. Its only entrypoint is @tanstack/react-table/legacy.
Read mappings for affected code
Audit finds
Read
Feature registration, row-model factories, function slots, bound methods, or consumed internals
Architecture mappings
getState, onStateChange, controlled ownership, observation, or reset changes
State mappings
Aggregation, logical pinning, sizing/resizing, sorting names, or selection predicates
Feature API mappings
Explicit generics, column helpers, scoped meta, registry augmentation, or RowData
TypeScript mappings
Complete audit checklist
Load the installed framework adapter's migration and table-state skills.
Replace the v8 adapter constructor/hook/controller with its v9 entrypoint.
Add a stable features object to every table.
Inventory every feature API used by table, row, column, cell, and header code; register each stock feature the table actually uses.
Use stockFeatures only as a temporary parity aid and record an explicit-feature follow-up.
Remove getCoreRowModel() unless supplying a deliberate custom coreRowModel slot.
Move all remaining get*RowModel() options (or a removed rowModels: {...} object, if present) to create*RowModel() feature slots.
Register each dependent feature before its row-model slot.
Move filterFns, sortingFns/sortFns, and aggregationFns into feature slots, registering individually imported built-ins; pass no registries to factories.
Register rowAggregationFeature independently and migrate custom aggregation callables to context-based AggregationFnDef definitions.
Register columnFilteringFeature before global filtering and filter/facet dependencies.
Register columnSizingFeature before columnResizingFeature.
Replace table.getState() and top-level onStateChange according to the adapter state guide.
Verify every controlled slice has an update path; verify externally owned atoms are reset by their owner.
Audit destructured, spread, serialized, or bare-callback instance methods.
Replace every column-pinning left/right key, argument, comparison, method family, and sticky CSS declaration with logical start/end equivalents.
Split table-level enablePinning; preserve column-def enablePinning where intended.
Split sizing/resizing features and rename the resizing state, setter, and callback.
Replace every sortingFn/SortingFn/sortingFns spelling with its v9 sort* spelling.
Remove every consumed underscore-prefixed internal API.
Recheck indeterminate selection logic against the new "at least one" semantics.
Add TFeatures to unavoidable explicit core types, helpers, and retained meta augmentation; otherwise restore inference.
Replace function-registry and filter-meta declaration merging with per-table slots where appropriate.
Ensure every row is a record or array under the stricter RowData constraint.
Migrate adapter-specific rendering, reactive data inputs, and subscription primitives.
Type-check without any/casts added merely to suppress migration failures.
Test sorting, filtering, faceting, grouping, expansion, pagination, selection, ordering, pinning, sizing, and resizing where enabled.
Test client/server ownership for every row-model pipeline stage and ensure manual modes receive already-processed data.
Test LTR and RTL layouts when column pinning or resizing is enabled.
Remove useLegacyTable after the incremental migration step that required it.
Completion checks
Missing feature APIs must be resolved through registration, not casts. Keep v8 get*RowModel configuration and physical pinning names out of the final v9 setup. Remove temporary stockFeatures or useLegacyTable use when the incremental step no longer needs them.
After behavior parity, consider tableOptions() for reusable configuration, createTableHook() for app conventions, narrower subscriptions, and scoped meta. These are optional improvements, not extra required breakages. Use the adapter's getting-started skill to reach its app-hook reference when adopting that pattern.
Installed API discovery
Start at node_modules/@tanstack/table-core/dist/index.d.ts and the relevant feature declarations. Resolve the installed package root if the package manager uses another layout. The adapter migration skill names its published declaration route; follow that route for framework APIs instead of applying another adapter's names.
1---2name: migrate-v8-to-v9-33description:4 Audit and migrate Table v8 to v9. Inventory affected APIs, follow the shared5 checklist, and read only the required architecture, state, feature, and TypeScript mappings.6metadata:7 source: https://skillmd.com/skills/tanstack/migrate-v8-to-v9-38 type: lifecycle9 library: '@tanstack/table-core'10 library_version: '9.3.1'11requires:12 - core13sources:14 - TanStack/table:docs/framework/react/guide/migrating.md15 - TanStack/table:docs/framework/preact/guide/migrating.md16 - TanStack/table:docs/framework/solid/guide/migrating.md17 - TanStack/table:docs/framework/svelte/guide/migrating.md18 - TanStack/table:docs/framework/vue/guide/migrating.md19 - TanStack/table:docs/framework/angular/guide/migrating.md20 - TanStack/table:docs/framework/lit/guide/migrating.md21 - TanStack/table:packages/table-core/src/index.ts22 - TanStack/table:packages/table-core/src/types/TableFeatures.ts23 - TanStack/table:packages/table-core/src/features/column-pinning/columnPinningFeature.types.ts24 - TanStack/table:packages/table-core/src/features/column-resizing/columnResizingFeature.types.ts25 - TanStack/table:packages/react-table/src/legacy.ts26---2728# Migrate Table v8 to v92930Read [core](../core/SKILL.md) first. Audit every item below before choosing detailed mappings. This shared checklist owns the complete core migration; the installed adapter's migration skill owns construction, rendering, framework requirements, and reactive wiring.3132## Procedure33341. Establish passing tests for the existing table and inventory its enabled interactions, imports, options, and state owners.352. Follow the whole audit checklist. Read a mapping reference when the audit finds affected code; preserve behavior while migrating features and construction.363. Load the installed adapter with `intent load <package>#migrate-v8-to-v9` and its `table-state` skill. Substitute the actual adapter package. React, Preact, Solid, Svelte, Vue, Angular, and Lit have migration skills; Alpine, Ember, and Octane have no v8 adapter migration journey.374. Type-check, exercise every enabled interaction and client/server stage, and complete the explicit v9 setup.3839Treat `useLegacyTable` as a deprecated React-only bridge for an existing incremental migration. It bundles every feature, can exceed the v8 bundle, and is not the target architecture. Its only entrypoint is `@tanstack/react-table/legacy`.4041## Read mappings for affected code4243| Audit finds | Read |44| ----------------------------------------------------------------------------------------------- | --------------------------------------------------- |45| Feature registration, row-model factories, function slots, bound methods, or consumed internals | [Architecture mappings](references/architecture.md) |46| `getState`, `onStateChange`, controlled ownership, observation, or reset changes | [State mappings](references/state.md) |47| Aggregation, logical pinning, sizing/resizing, sorting names, or selection predicates | [Feature API mappings](references/feature-apis.md) |48| Explicit generics, column helpers, scoped meta, registry augmentation, or `RowData` | [TypeScript mappings](references/typescript.md) |4950## Complete audit checklist5152- [ ] Load the installed framework adapter's migration and table-state skills.53- [ ] Replace the v8 adapter constructor/hook/controller with its v9 entrypoint.54- [ ] Add a stable `features` object to every table.55- [ ] Inventory every feature API used by table, row, column, cell, and header code; register each stock feature the table actually uses.56- [ ] Use `stockFeatures` only as a temporary parity aid and record an explicit-feature follow-up.57- [ ] Remove `getCoreRowModel()` unless supplying a deliberate custom `coreRowModel` slot.58- [ ] Move all remaining `get*RowModel()` options (or a removed `rowModels: {...}` object, if present) to `create*RowModel()` feature slots.59- [ ] Register each dependent feature before its row-model slot.60- [ ] Move `filterFns`, `sortingFns`/`sortFns`, and `aggregationFns` into feature slots, registering individually imported built-ins; pass no registries to factories.61- [ ] Register `rowAggregationFeature` independently and migrate custom aggregation callables to context-based `AggregationFnDef` definitions.62- [ ] Register `columnFilteringFeature` before global filtering and filter/facet dependencies.63- [ ] Register `columnSizingFeature` before `columnResizingFeature`.64- [ ] Replace `table.getState()` and top-level `onStateChange` according to the adapter state guide.65- [ ] Verify every controlled slice has an update path; verify externally owned atoms are reset by their owner.66- [ ] Audit destructured, spread, serialized, or bare-callback instance methods.67- [ ] Replace every column-pinning `left`/`right` key, argument, comparison, method family, and sticky CSS declaration with logical start/end equivalents.68- [ ] Split table-level `enablePinning`; preserve column-def `enablePinning` where intended.69- [ ] Split sizing/resizing features and rename the resizing state, setter, and callback.70- [ ] Replace every `sortingFn`/`SortingFn`/`sortingFns` spelling with its v9 `sort*` spelling.71- [ ] Remove every consumed underscore-prefixed internal API.72- [ ] Recheck indeterminate selection logic against the new "at least one" semantics.73- [ ] Add `TFeatures` to unavoidable explicit core types, helpers, and retained meta augmentation; otherwise restore inference.74- [ ] Replace function-registry and filter-meta declaration merging with per-table slots where appropriate.75- [ ] Ensure every row is a record or array under the stricter `RowData` constraint.76- [ ] Migrate adapter-specific rendering, reactive data inputs, and subscription primitives.77- [ ] Type-check without `any`/casts added merely to suppress migration failures.78- [ ] Test sorting, filtering, faceting, grouping, expansion, pagination, selection, ordering, pinning, sizing, and resizing where enabled.79- [ ] Test client/server ownership for every row-model pipeline stage and ensure manual modes receive already-processed data.80- [ ] Test LTR and RTL layouts when column pinning or resizing is enabled.81- [ ] Remove `useLegacyTable` after the incremental migration step that required it.8283## Completion checks8485Missing feature APIs must be resolved through registration, not casts. Keep v8 `get*RowModel` configuration and physical pinning names out of the final v9 setup. Remove temporary `stockFeatures` or `useLegacyTable` use when the incremental step no longer needs them.8687After behavior parity, consider `tableOptions()` for reusable configuration, `createTableHook()` for app conventions, narrower subscriptions, and scoped meta. These are optional improvements, not extra required breakages. Use the adapter's getting-started skill to reach its app-hook reference when adopting that pattern.8889## Installed API discovery9091Start at `node_modules/@tanstack/table-core/dist/index.d.ts` and the relevant feature declarations. Resolve the installed package root if the package manager uses another layout. The adapter migration skill names its published declaration route; follow that route for framework APIs instead of applying another adapter's names.
Run npx get-skill add tanstack/migrate-v8-to-v9-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Audit and migrate Table v8 to v9. Inventory affected APIs, follow the shared checklist, and read only the required architecture, state, feature, and TypeScript mappings. It is listed under AI & ML on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
TanStack (@tanstack) published this skill. Their other Agent Skills are listed on their SkillMD profile.