svelte/migrate-v8-to-v9

What problem does it solve?

It resolves the breaking changes between @tanstack/svelte-table v8 and v9 by guiding a mechanical but thorough migration, especially the required move to Svelte 5 runes and the new table creation/state/row-model architecture.

Core Features & Use Cases

• Svelte 5 prerequisite validation: Ensures you recognize that v9 is a full rewrite and will not work on Svelte 3/4, preventing compile-time failures.
• API migration mapping: Converts v8 constructs like createSvelteTable, get*RowModel factories, monolithic onStateChange, and flexRender usage into v9 equivalents such as createTable, _rowModels registration, per-slice on[State]Change/atoms, and FlexRender.
• State ownership rewrite: Helps you choose and implement the correct v9 state model per slice (internal initialState, external state callbacks, or external atoms with precedence rules).
• Rendering and cell integration updates: Updates custom component and snippet rendering patterns to v9’s renderComponent/renderSnippet workflow.

Quick Start

Ask an AI coding agent to migrate a Svelte 5 component that uses @tanstack/svelte-table@8 by applying the v8-to-v9 changes listed here, including table creation, feature registration, row-model wiring, state ownership, and FlexRender-based rendering.