svelte/migrate-v8-to-v9

To migrate, replace createSvelteTable and get*RowModel factories with the v9 createTable API, register _features and _rowModels, update monolithic onStateChange to per-slice on[State]Change callbacks or external atoms, and switch flexRender to FlexRender.

TanStack Svelte Table v9 requires Svelte 5 runes because it is a full rewrite that will not work on Svelte 3 or 4. Validating your Svelte 5 prerequisite prevents compile-time failures during the migration process.

Handling state ownership when upgrading to v9 requires choosing and implementing the correct state model per slice using internal initialState, external state callbacks via on[State]Change, or external atoms with specific precedence rules.

The best way to update flexRender usage for Svelte Table v9 is to transition to the v9 FlexRender API and update custom component and snippet rendering patterns to the new renderComponent and renderSnippet workflow.

Registering row models in TanStack Svelte Table v9 involves using the new createTable API and explicitly wiring your _features and _rowModels during table creation instead of using the old v8 get*RowModel factory pattern.

Your TanStack Svelte Table v8 migration is failing after updating to v9 due to breaking changes from the full rewrite. You must replace v8 constructs like createSvelteTable and monolithic onStateChange with v9 rune-based equivalents to resolve compile errors.