Article: TanStack has officially stopped using React Server Components (RSC) in its libraries, citing added complexity, reduced flexibility, modest performance gains, and slower development velocity as decisive factors. The move matters for anyone building React-based tools, because TanStack’s libraries are widely adopted and often set practical standards for the ecosystem.

Why RSC seemed attractive

React Server Components arrived as a way to shift heavy data-fetching and rendering work to the server, promising smaller client bundles and faster page loads. The TanStack team tried the approach, hoping to improve the user experience of their data-grid and query libraries.

What pushed them away

  • Complexity – Debugging RSC code forced a separate mental model. The team spent more time tracing server-side rendering issues than they could afford.
  • Flexibility – Many third-party libraries assume a pure client environment. RSC’s server-only execution made integration difficult without rewriting or shimming those dependencies.
  • Performance – Measured speed improvements were modest. The overhead of orchestrating server and client boundaries outweighed the marginal gains in most real-world scenarios.
  • Velocity – Simpler, client-only patterns let the team ship updates faster. With RSC, every change required validation on both server and client, slowing the release cycle.

The broader stakes

If a leading toolkit like TanStack steps back from RSC, other projects may reconsider the hype. The decision highlights a trade-off: cutting-edge features can introduce hidden costs that hurt developer productivity and long-term maintenance. Companies that prioritize rapid iteration and broad library compatibility might follow suit.

Counter-point

Some developers still see value in RSC for specific use cases—especially where server-side data processing can dramatically reduce payload size. The approach may evolve, and future tooling could address the pain points TanStack identified. For now, the consensus remains mixed.

What to watch next

  • Tooling updates – Improvements in debugging and integration support could lower the complexity barrier.
  • Community feedback – As more teams share performance data, the cost-benefit equation may shift.
  • Alternative patterns – Incremental server rendering techniques or hybrid approaches might offer a middle ground.

Takeaway: TanStack’s retreat from React Server Components reminds us that newer isn’t always better; developers should weigh the real cost to their workflow against the promised gains before adopting emerging patterns.

Source: https://tanstack.com/blog/we-stopped-using-rsc-on-tanstack-com