# Migrate V8 To V9

Migrate svelte Table v8 to v9.

- Repository: https://github.com/TanStack/table (28539 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-21
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add TanStack/table --skill migrate-v8-to-v9 -g -a claude-code -y`
Codex: `npx skills add TanStack/table --skill migrate-v8-to-v9 -g -a codex -y`
Cursor: `npx skills add TanStack/table --skill migrate-v8-to-v9 -g -a cursor -y`
Gemini CLI: `npx skills add TanStack/table --skill migrate-v8-to-v9 -g -a gemini-cli -y`

## Description

Migrate svelte Table v8 to v9. Audit framework construction, rendering, state, and app hooks, with shared API changes in the core migration skill.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Svelte 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 Svelte-specific changes.

Framework prerequisite: Svelte 5 (`svelte ^5.0.0`); migrate Svelte 3/4 components before Table.

## Adapter audit

- [ ] Upgrade to Svelte 5 and replace old writable-store table setup with runes/getters.
- [ ] Replace `createSvelteTable` with `createTable`; preserve changing data and controlled slices through getters.
- [ ] Configure explicit features/row-model slots and complete the shared core checklist.
- [ ] Remove creation selectors, selected `table.state`, `subscribeTable`, and `SubscribeSource` from earlier v9 code.
- [ ] Update `SvelteTable` to two generic parameters and `AppSvelteTable` to five; remove selected-state generics from `useTableContext`.
- [ ] Read atoms/store in templates or tracked runes. Use per-slice updater callbacks, `createTableState`, or external Svelte Store atoms instead of global `onStateChange`.
- [ ] Render with `FlexRender`, `renderComponent`, or `renderSnippet`. Use the shipped rune-aware `createTableHook` only for repeated conventions.

## Load the affected details

When the audit finds old Svelte construction, state, rendering, or app-hook code, read [adapter migration details](references/adapter-migration.md) before editing it. For a replacement render scaffold, read [getting started](../getting-started/SKILL.md). For controlled or stale state after migration, read [table state](../table-state/SKILL.md).

Shared pinning, sizing, sorting, selection, prototype-method, type, and registry changes stay in the core migration references. Renaming `createSvelteTable` alone does not complete the migration.

## Verify the migration

The rest: https://github.com/TanStack/table/blob/HEAD/packages/svelte-table/skills/migrate-v8-to-v9/SKILL.md