CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

migrate-v8-to-v9

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

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/preact-table/skills/migrate-v8-to-v9/SKILL.md
SKILL.md
Quality
Evals
Security

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

Framework prerequisite: Preact 10 or newer (preact >=10).

Adapter audit

  • Replace React-adapter imports and useReactTable with native @tanstack/preact-table and useTable.
  • Remove compat aliases that existed only for Table. Preserve aliases still required by other libraries, including a React Virtual integration.
  • Keep model inputs stable and configure explicit features/row-model slots; complete the shared core checklist.
  • Use selected table.state, table.Subscribe, or Preact Store subscriptions; snapshots alone do not rerender consumers.
  • Pair controlled slices with callbacks, or supply stable atoms from @tanstack/preact-store; remove global onStateChange.
  • Use native Preact FlexRender components. Adopt tableOptions or createTableHook only for repeated app conventions.

Load the affected details

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

Verify the migration

  • Type-check against the installed v9 adapter and exercise every enabled client/manual feature flow.
  • Verify external state writes, reactive data replacement, and the framework rendering paths changed above.
  • Complete the core checklist, including layout and selection behavior when those features are used.
  • Replace temporary stockFeatures when the target is explicit feature tree-shaking.

API discovery

Inspect node_modules/@tanstack/preact-table/dist/index.d.ts and the exported adapter declarations. Use node_modules/@tanstack/table-core/dist/index.d.ts for shared APIs.

Repository

TanStack/table

Path

packages/preact-table/skills/migrate-v8-to-v9/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.