api-not-found

Diagnose missing TanStack Table v9 exports, options, state slices, and instance methods.

28.4k|3.6k|Updated Oct 20, 2016
One-click install
npx skills add https://github.com/TanStack/table --skill api-not-found
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-not-found
Source: https://github.com/TanStack/table/tree/main/packages/table-core/skills/api-not-found
Command: npx skills add https://github.com/TanStack/table --skill api-not-found

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When working with TanStack Table v9, developers hit type errors, undefined feature methods, or missing exports—often because they rely on remembered v8 APIs or outdated examples. This Skill diagnoses those failures by treating the installed package as the exact API truth instead of guessing.

Core Features & Use Cases

  • Export Tracing: Trace any missing export back to its source in the installed dist/index.d.ts files of @tanstack/table-core or framework adapters.
  • Feature Gating Checks: Verify whether an API is absent because the corresponding feature was omitted from the tableFeatures registry, not because it was removed.
  • v8-to-v9 Migration Fixes: Correct common mistakes like using getSortedRowModel() instead of the v9 create* factories and named feature slots.
  • Use Case: Your code throws a type error on row.getValue after upgrading to v9. Use this Skill to inspect the installed package, discover that instance methods live on prototypes, and fix the call pattern.

Quick Start

Ask the AI to diagnose why a TanStack Table v9 export or instance method is missing by inspecting the installed package in node_modules.

Frequently Asked Questions about api-not-found

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

FAQPage Schema
How do I fix a missing export error in TanStack Table v9?

Search the installed package with ripgrep against node_modules/@tanstack/table-core/dist/ to confirm whether the export exists. If it exists but the instance API does not, check the feature registry in TableFeatures.ts to see if the feature was registered.

How to migrate getSortedRowModel from TanStack Table v8 to v9?

V9 replaced get* row-model factories with create* factories registered as named feature slots. Use tableFeatures({ rowSortingFeature, sortedRowModel: createSortedRowModel() }) instead of passing getSortedRowModel() in options.

Why does Object.keys not show TanStack Table row methods?

V9 shares many instance methods through prototypes, so spread, serialization, and Object.keys omit them. Call methods directly on the instance, such as row.getValue('name'), or inspect Object.getPrototypeOf(row).

Does TanStack Table v9 remove APIs that existed in v8?

Often the API still exists but is gated behind feature registration. Optional APIs and state are typed and installed from the concrete feature registry, so an empty tableFeatures({}) call makes them appear removed.

Where should I look for the correct TanStack Table adapter API?

Check the installed adapter's dist/index.d.ts first, then the core dist/index.d.ts. Ember uses declarations*.d.ts and Angular uses dist/types/*.d.ts. Always prefer the installed package version over remembered documentation.