Solid 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 Solid-specific changes.

Framework prerequisite: Solid 1.3 or newer (solid-js >=1.3).

Adapter audit

• Replace createSolidTable with createTable in a Solid owner.
• Keep features and columns stable; preserve changing data and controlled state through getters.
• Configure explicit features/row-model slots and complete the shared core checklist.
• Replace getState() with narrow tracked atom reads, or intentional whole-store reads. Remove global onStateChange.
• Pair a controlled getter with its Solid setter, or supply a Solid Store atom. Handle both value and functional updater forms.
• Keep atom reads inside JSX, memos, or effects. Replace deprecated table.Subscribe wrappers with direct table.atoms reads. Component bodies are untracked.
• Replace function rendering with FlexRender components; adopt tableOptions and createTableHook only for repeated conventions.

Load the affected details

When the audit finds old Solid 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 createSolidTable alone does not complete the migration.

Verify the migration