April 13, 2026
Framework Fight Night
TanStack Start Now Support React Server Components
TanStack Start adds server-side superpowers — fans yell “Next who?” while skeptics pump the brakes
TLDR: TanStack Start now supports React Server Components in a flexible, data‑stream style that avoids heavy framework rules. The community is split between “Next.js killer” cheers, “bring back simple templates” nostalgia, and skeptics asking why offload work to servers at all—signaling a real shake‑up in how web apps might be built next.
TanStack Start just rolled out support for React Server Components (RSCs) — and the comments section immediately turned into Framework Fight Night. In simple terms, RSCs let apps do heavy work on the server so your phone or laptop doesn’t sweat. TanStack’s twist: treat RSCs like simple “streams” you can fetch and cache on your own terms, not a bossy system that controls your whole app. Think less lock‑in, more plug‑and‑play. If you’re curious, here’s the official RSC explainer: React docs, and TanStack’s home base: tanstack.com/start.
The hype squad arrived first. One fan literally said it was so pretty they nearly cried, then declared this could replace Next.js, blaming “VC money” if it doesn’t. Another dev praised the smooth developer experience and called Next “bloated,” urging folks to try TanStack Start. But the old guard fired back: “Can we just go back to simple templates like PHP and only use JavaScript for buttons?” Meanwhile, skeptics questioned the whole idea: why shove heavy rendering onto “a wimpy AWS box” when users have powerful MacBooks and iPhones?
Between nostalgia for 2000s‑style templates, dreams of a Next.js dethroning, and wishlists for Preact support, the memes flowed: “Framework fatigue bingo,” “90s PHP called,” and plenty of “crying in JSX.” In other words: drama served hot.
Key Points
- •TanStack Start adds support for React Server Components (RSC) by treating them as React Flight streams.
- •The approach lets clients fetch, cache, and render RSCs on demand, rather than relying on a server-owned component tree.
- •RSCs are positioned for heavy or infrequently changing tasks (e.g., markdown parsing, syntax highlighting, date formatting) that benefit from server execution and granular caching.
- •Developers can create RSC streams in server functions or API routes, decode them during SSR or on the client, and cache them with existing tools.
- •TanStack Query is used to manage fetching and caching of RSC streams, integrating RSCs into typical data workflows.