solid/migrate-v8-to-v9

Migrate @tanstack/solid-table v8 code to v9 APIs and state patterns.

28.3k|3.6k|Updated Oct 20, 2016
One-click install
npx skills add https://github.com/TanStack/table --skill solid-migrate-v8-to-v9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solid/migrate-v8-to-v9
Source: https://github.com/TanStack/table/tree/main/packages/solid-table/skills/solid/migrate-v8-to-v9
Command: npx skills add https://github.com/TanStack/table --skill solid-migrate-v8-to-v9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you upgrade from @tanstack/solid-table v8 to v9 by walking you through the key breaking changes so your tables compile and behave correctly after the migration.

Core Features & Use Cases

  • Adapter API migration: Rename createSolidTable to createTable and adjust required inputs for v9.
  • Feature and row-model refactor: Register _features via tableFeatures(...) and move all getRowModel options into _rowModels using createRowModel factories.
  • State model update for Solid: Use atom-based ownership via atoms or Solid-idiomatic reactive state patterns (including table.state() accessor semantics).

Quick Start

Update each v8 table incrementally by renaming createSolidTable to createTable, introducing _features with tableFeatures(...), moving every getRowModel option into _rowModels, and switching sortingFn to sortFn while adopting per-slice onChange or atoms.

Frequently Asked Questions about solid/migrate-v8-to-v9

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate TanStack Solid Table from v8 to v9?

Migrate TanStack Solid Table from v8 to v9 by renaming createSolidTable to createTable, moving get*RowModel options into _rowModels using create*RowModel factories, and registering _features via tableFeatures(). You must also update state ownership to use per-slice on*Change handlers or atoms.

What breaking changes were introduced in TanStack Table v9 for Solid?

TanStack Table v9 breaking changes include renaming createSolidTable to createTable, requiring _features via tableFeatures(), moving row models into _rowModels, renaming sortingFn to sortFn, and removing whole-state onStateChange in favor of per-slice handlers or atoms.

Why did my Solid Table row models break after upgrading to v9?

Solid Table row models broke in v9 because get*RowModel options were moved into the _rowModels object. You must now supply create*RowModel factories inside _rowModels instead of passing them as top-level options to the table initialization function.

How do I handle state ownership changes when upgrading Solid Table to v9?

Handle Solid Table v9 state ownership by replacing the removed whole-state onStateChange with per-slice on*Change handlers or atom-based reactive state. This update requires adopting Solid-idiomatic table.state() accessor semantics to preserve sorting and filtering behavior.

Do I need to update column helper generics for TanStack Table v9?

Yes, you must fix createColumnHelper generics when migrating to TanStack Table v9. The typing contracts changed during the initialization refactor, requiring updates to ensure your datagrid columns compile and behave correctly.

Can I preserve sorting and filtering behavior when migrating Solid Table to v9?

You can preserve sorting and filtering behavior during a Solid Table v9 migration by adopting the sortFn and filterFn renames alongside per-slice on*Change handlers. This ensures your datagrid state initialization and reactive patterns remain functional.