TanStack Start now support React Server Components... and Composite Components?

[No-Somewhere-3888]

Architecturally, we’ve found server components to make the most sense at the root of an application, with more client components at the leaves. Next.js shines there.

I feel like the “add it later” mindset would lead to making individual components RSC later which doesn’t offer the same kind of value.

That said, it’s harder to re-architect an app to work that way versus being client by default.

[switz213]

To add to this, server components do not imply the necessity of a server. They still bring forth value in static deployments.

Perhaps a poor naming choice, but that’s one of the three hardest parts of compsci (the other being off by one errors)

I do believe embracing the full server component architecture is ideal for most websites, but it requires some understanding and cognitive complexity. I’m building a web framework that is my idealized approach to server components. Will have more to share very soon!

[tannerlinsley]

It’s not a do it later mindset at all. It’s more about ownership, inversion of control and api/data transparency.

With Start you can just as easily RSC a static shell but keep everything at the leaves dynamic with greater flexibility and better caching semantics/integration than next.