TanStack Start embraces React Server Components — but on your terms

TanStack announced in a blog post by Manuel Schiller, Tanner Linsley, and Jack Herrington that TanStack Start now supports React Server Components (RSCs), with a twist: the client gets to call the shots. The team says RSCs are treated as plain React Flight streams you can fetch, cache, and compose from the client instead of being locked into a server-owned component tree. Short version: more control for developers, less opaque framework magic.
What changed
Rather than force a server-first app model where the framework dictates rendering boundaries and recomposition, TanStack Start presents RSC output as just another async resource — similar to fetching JSON. React renders to a Flight stream on the server; the client decodes that stream into React elements. There’s no extra protocol, the post argues, and the API surface is intentionally small. It also has been reported that TanStack will lean on TanStack Query to handle server synchronization and caching logic for these streams.
Why it matters
This is a philosophical pivot as much as a technical one. Frameworks that treat RSCs as the axis around which an app must orbit can be neat — but they can also feel like buying a ticket to a proprietary amusement park. TanStack’s approach aims to make RSCs composable and interoperable: cache them in memory, a database, a CDN, or the client — whatever fits your workflow. That makes heavy rendering logic (markdown parsing, syntax highlighting, content transforms) easier to move off the client without handing the keys to a single framework.
In practice this could simplify caching and deployment patterns while keeping streaming first-class. Developers who’ve wanted server-rendered UI as consumable data rather than a framework mandate will find this appealing. Is it a silver bullet? No. But it’s a clear bet on modularity and developer control at a time when the community is debating how much control frameworks should really take.
Sources: tanstack.com, Hacker News
Comments