Migrate preact Table v8 to v9. Audit framework construction, rendering, state, and app hooks, with shared API changes in the core migration skill.
79%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
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.mdBefore 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).
useReactTable with native @tanstack/preact-table and useTable.table.state, table.Subscribe, or Preact Store subscriptions; snapshots alone do not rerender consumers.@tanstack/preact-store; remove global onStateChange.tableOptions or createTableHook only for repeated app conventions.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.
stockFeatures when the target is explicit feature tree-shaking.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.
TanStack/table
c14e022
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.