TanStack Ecosystem
TanStack is the frontend data and routing ecosystem route when the work names Query, Router, Table, Form, Start, or cache/state behavior around server data in React apps. Source: Ecosystem Capability Coverage, 2026-06-27
When To Use This
Use TanStack when the problem is client/server data synchronization, query caching, mutation invalidation, type-safe routing, tables, or frontend data-loading ergonomics. It is a library ecosystem, not a SaaS product route. Source: Ecosystem Capability Coverage, 2026-06-27
Decision Matrix
| Need | Route | Verification |
|---|---|---|
| Server-state cache | TanStack Query docs/patterns | Query/mutation tests |
| Type-safe routing | TanStack Router docs/patterns | Route typecheck and browser smoke |
| Complex tables | TanStack Table docs/patterns | Sorting/filtering/pagination tests |
| Full-stack framework | TanStack Start docs/patterns | Build and route smoke |
| Modern web VPS stack | Modern Web VPS Stack | Pinned package versions, SSR/stream smoke, host adapter proof |
Core Model
TanStack should be separated from backend/data vendors. Supabase, Firebase, ClickHouse, and Neon own data systems; TanStack owns frontend cache, routing, and data interaction patterns. The boundary is user interaction and client state, not storage. Source: User request, 2026-06-27; Ecosystem Capability Coverage
Modern Web Stack Role
TanStack Router/Start is the route-first alternative to framework selection by habit. Start keeps Router as the application contract, then adds full-document SSR, streaming, server functions, server routes, middleware, and deployable runtime output. It can target Node, Workers, Netlify, Railway, and other host adapters, so the app model can stay stable while deployment moves between Cloudflare Ecosystem, Coolify, Hetzner, or a managed PaaS. Source: TanStack Start, 2026-07-06
Use Modern Web VPS Stack when the user asks for TanStack Router/Start with Tailwind, Vite/Rolldown, Cloudflare, Hetzner, or self-hosted VPS deployment. TanStack Start is still marked RC; production projects should pin Start/Router packages and treat version bumps as planned work. Source: TanStack Start RC guidance, 2026-07-06
Version Snapshot
Checked 2026-07-06 against the npm registry:
| Package | Latest | Published |
|---|---|---|
@tanstack/react-router |
1.170.17 |
2026-07-01 |
@tanstack/react-start |
1.168.27 |
2026-07-01 |
@tanstack/router-plugin |
1.168.19 |
2026-07-01 |
Pin exact versions for production Start work and re-run route, loader, server-function, SSR, and browser smoke checks after upgrades. Source: npm registry and TanStack Start, 2026-07-06
Routing Summary
Preferred order: project-local package version and docs, then frontend/react skills, then official TanStack examples. There is no first-party CLI in the local seed catalog, so do not pretend it behaves like a service ecosystem. Source: Ecosystem Capability Coverage, 2026-06-27; config/capability-harvest-seeds.json
Failure Modes
- Confusing server state with local UI state.
- Invalidating too broadly and hiding performance bugs.
- Treating route loaders as a backend authorization layer.
- Choosing TanStack because it is fashionable rather than because the app needs its model.
Verification Path
Run typecheck, unit tests around query/mutation behavior, and browser smoke for routes/tables. For cache work, prove loading, success, error, invalidation, and stale-data states. Source: Skill Resolver, 2026-06-27
Timeline
- 2026-07-06 | Added the TanStack role in Modern Web VPS Stack: Router/Start as the route-first app contract for Tailwind/Vite apps that may deploy to Node, Workers, or self-hosted VPS infrastructure. Refreshed package snapshot for Router, Start, and router-plugin. Source: User request, TanStack docs, npm registry, 2026-07-06
- 2026-06-27 | Canonical ecosystem page created after the coverage audit showed TanStack had skills.sh signal but no dedicated routing/page surface. Source: User request, 2026-06-27; Ecosystem Capability Coverage