TanStack Start is one of the most anticipated React meta frameworks heading into its 1.0 release — and in this episode, I sit down with Tanner Linsley, the creator of TanStack, to go deep on the architecture, API design, and philosophy behind it.

We build an app from scratch using the TanStack CLI, walk through file-based routing (flat, directory, hybrid — it's wildly flexible), explore loaders, server functions, and then Tanner drops something brand new: Composite Components — a primitives-first approach to React Server Components where the client stays in control.

If you're coming from Next.js or Remix and want to understand how TanStack Start thinks differently about the server/client boundary, this one's for you.

⏱ Timestamps
0:00 – AI coding tools: OpenCode, Claude Code & Opus 4.5
6:22 – Managing terminals is the new developer workflow
7:08 – Vibe coding and non-developers entering the terminal
9:39 – N8N, personal AI assistants & what's coming in 2026
11:14 – Intro: Who is Tanner Linsley & what is TanStack Start
14:10 – SSR by default, streaming, and the SPA handoff
15:24 – File-based routing deep dive (directories, flat, hybrid)
22:01 – Adapters: Cloudflare, Netlify, Nitro & Vite-native plugins
25:09 – Route configuration: loaders, metadata — all in one file
27:16 – Type safety without code generation
31:23 – Customizable route tokens (recreating Next.js conventions)
35:06 – Virtual file routes & mixing routing strategies
37:20 – Data fetching with loaders (isomorphic by default)
42:45 – Why loaders run on both server AND client
44:22 – Server functions with createServerFunction
48:35 – Dead code elimination & server/client bundling
53:34 – React Server Components vs. server functions
55:41 – RSC as data: caching, invalidation & granularity
59:33 – Building a server component in TanStack Start
1:09:04 – Client-first philosophy: "You're always on the client"
1:11:02 – Composite Components: a new React primitive (exclusive)
1:18:14 – Inversion of control: the client decides what renders
1:21:51 – Flight data, slots, and render props across the server/client gap
1:25:00 – Why this paradigm is simpler than traditional RSC
1:30:25 – TanStack Start 1.0 timeline (Q1 2026)
1:32:27 – Documentation overhaul & AI agent skills for TanStack

🔗 Links
TanStack Start Docs: https://tanstack.com/start/latest
TanStack Builder (alpha): https://tanstack.com/builder
TanStack Router Docs: https://tanstack.com/router/latest
TanStack Query Docs: https://tanstack.com/query/latest
Tanner Linsley on X/Twitter: https://x.com/tannerlinsley
TanStack GitHub: https://github.com/TanStack

📌 Topics Covered
TanStack Start, TanStack Router, React meta framework, React Server Components, composite components, file-based routing, server functions, createServerFunction, SSR, streaming, hydration, SPA, type safety, TypeScript, Vite, Cloudflare Workers, Netlify, Nitro, React Query, TanStack Query, TanStack CLI, Next.js alternative, Remix alternative, full-stack React, client-first framework, dead code elimination, RSC flight data, caching, invalidation

#TanStackStart #React #ReactServerComponents #WebDevelopment #TannerLinsley #TypeScript #JavaScript #FullStackReact #TanStack #MetaFramework

Hamed Bahram

A deep-dive conversation with Tanner Lindsey, creator of TanStack, covering TanStack Start's architecture as a meta-framework built on TanStack Router. Topics include file-based routing conventions (flat files, directories, dot notation, customizable tokens), isomorphic loaders vs. server functions, how server functions differ from React Server Components, and a preview of TanStack's upcoming composite component API that inverts control from server to client for granular caching and slot-based composition.

TanStack Start: Server Components Without the Mental Gymnastics