
Migrate V8 To V9
Migrate lit Table v8 to v9.
Install
npx skills add TanStack/table --skill migrate-v8-to-v9 -g -a claude-code -y- Repository
- TanStack/table28.5k
- Category
- Engineering
- Updated
- 14d ago
- License
- MIT
- Context cost
- Lightabout 522 tokens
- Runs scripts
- No, instructions only
What it does
Migrate lit Table v8 to v9. Audit framework construction, rendering, state, and app hooks, with shared API changes in the core migration skill.
Load intent load @tanstack/table-core#migrate-v8-to-v9 first and audit its entire shared checklist. It owns feature registration, row-model slots, state/reset changes, prototype methods, logical pinning, sizing/resizing, sorting, selection, helpers, and TypeScript mappings.
Framework prerequisites
Lit 3.1.3 or newer within v3 (lit ^3.1.3) and @lit/context ^1.1.0 are required.
Lit migration checklist
- Construct one
TableController<typeof features, TData>(this)as a stable host field. - Replace the v8
controller.tableproperty/options thunk withcontroller.table(options, selector?)during render. - Read selected
table.statefor rendering; use atom snapshots in handlers or stabletable.subscribeselectors for template regions. - Feed resolved controlled callbacks back through reactive Lit properties, or use stable external atoms.
- Switch render helpers to
FlexRender({ cell }),FlexRender({ header }), orFlexRender({ footer })and preserve instance-method receivers. - If app conventions repeat, construct a host-bound
useAppTableonce and call its.table()during render.
Apply the affected mappings
Read adapter-migration when changing construction, rendering, state, or app hooks. Read the relevant core migration references for each affected shared API; this adapter checklist does not replace that audit.
For complete v9 construction examples, read getting-started. For reactive state repairs, read table-state.
Final checks
- All shared core migration checks and affected mappings have been applied.
- The framework checklist above passes with the current adapter declarations.
- Model inputs remain stable and state changes reach their reactive owner.
