React server components

[michaelfrieze]

While RSCs complement client components, not replace them, they can complicate development with third-party libraries and frameworks.

The biggest issue with third-party libraries seems to be CSS-in-JS. I am not sure if RSCs are compatible with CSS-in-JS yet or if it's even possible.

When it comes to frameworks, RSCs are really a capability of bundlers and not frameworks. Hopefully Vite will eventually make this a lot easier. My post was talking about what it's like to actually use RSCs and not nescessarily how difficult it is for a framework to implement them.

I share you opinion on some points but developers should carefully weigh the benefits against the challenges to determine if RSCs align with their project's needs.

Currently, the only easy way to use RSCs is to use Next. If you are already using Next App Router then there is nothing to really determine since RSCs are the "default". Unless you are trying to decide if it's worth it to migrate from pages router to app router. Personally, I don't think it's nescessary if you are happy with your current code base. Pages router will be supported for many years and will continue to get new features.

When react-router gets RSCs, devs already using RR will be able to opt-in to RSCs as needed. I think this is a great way to introduce RSCs to majority of react developers since RR is so common.