Migrate vue Table v8 to v9. Audit framework construction, rendering, state, and app hooks, with shared API changes in the core migration skill.
76%
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/vue-table/skills/migrate-v8-to-v9/SKILL.mdBefore starting, run intent load @tanstack/table-core#migrate-v8-to-v9. Audit its entire shared checklist and read the detailed core mappings for APIs present in the application. This checklist adds the Vue-specific changes.
Framework prerequisite: Vue 3.2 or newer (vue >=3.2).
useVueTable with useTable and preserve ref/computed/getter inputs.getState() with tracked atom reads or intentional whole-store reads. Use computed for derived template values.onStateChange.table.Subscribe calls with native reactive reads. Use a child component when you need to preserve a separate component render boundary.tableOptions or createTableHook only for repeated conventions and explicit context-hook export types when needed to break circular inference.When the audit finds old Vue construction, state, rendering, or app-hook code, read adapter migration details before editing it. For a replacement render scaffold, read getting started. For controlled or stale state after migration, read table state.
Shared pinning, sizing, sorting, selection, prototype-method, type, and registry changes stay in the core migration references. Renaming useVueTable alone does not complete the migration.
stockFeatures when the target is explicit feature tree-shaking.Inspect node_modules/@tanstack/vue-table/dist/index.d.ts and the exported adapter declarations. Use node_modules/@tanstack/table-core/dist/index.d.ts for shared APIs.
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.