Migrate lit Table v8 to v9. Audit framework construction, rendering, state, and app hooks, with shared API changes in the core migration skill.
77%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./packages/lit-table/skills/migrate-v8-to-v9/SKILL.mdLoad 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.
Lit 3.1.3 or newer within v3 (lit ^3.1.3) and @lit/context ^1.1.0 are required.
TableController<typeof features, TData>(this) as a stable host field.controller.table property/options thunk with controller.table(options, selector?) during render.table.state for rendering; use atom snapshots in handlers or stable table.subscribe selectors for template regions.FlexRender({ cell }), FlexRender({ header }), or FlexRender({ footer }) and preserve instance-method receivers.useAppTable once and call its .table() during render.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.
Inspect node_modules/@tanstack/lit-table/dist/index.d.ts, then TableController.d.ts, flexRender.d.ts, or the relevant exported declaration. Core feature APIs are in node_modules/@tanstack/table-core/dist/features/.
TanStack/table
c14e022
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.