Vue v8-to-v9 migration checklist

Before 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).

Adapter audit

• Replace useVueTable with useTable and preserve ref/computed/getter inputs.
• Keep features and columns stable, configure explicit features/row-model slots, and complete the shared core checklist.
• Replace getState() with tracked atom reads or intentional whole-store reads. Use computed for derived template values.
• Pair controlled reactive values with callbacks that resolve both updater forms, or supply stable Vue Store atoms. Remove global onStateChange.
• Replace deprecated table.Subscribe calls with native reactive reads. Use a child component when you need to preserve a separate component render boundary.
• Adopt FlexRender cell/header/footer shorthand; the old render/props shape remains supported.
• Use tableOptions or createTableHook only for repeated conventions and explicit context-hook export types when needed to break circular inference.

Load the affected details

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.

Verify the migration