feat(rsc-streaming): Integrating RSC builds with Streaming and Client side hydration

[dac09]

Integrates streaming ssr builds with RSC. Note in it's current form when RSC is enabled, the pages are not SSR'd. Working that out now.

We now generate three different builds:

• RSC client (which is different to regular client!)
• Server (for streaming)
• RSC (for worker)

I've also changed the build process to output into their respective folders.

👉 The RSC build process no longer works in isolation, and will use existing Vite configuration. This means Tailwind etc. will work (even if its inefficient how the CSS is loaded). See changes here: dac09#262

Outstanding:

• Unhardcode paths
• Inject webpack shims for RSC via streaming server or vite plugin
• Understand (but not implement if complicated) - what happens when you have page imports
• Can we get it working without needing index.html?
• Make e2e tests pass again! RSC+Streaming+Client works but the regular client-side/SPA does not 🤣

What will be out of scope in this PR
✋ combining all the various vite settings into the rw-vite-plugin
I managed to do this, and in order to help myself get further with the e2e failures we're seeing I merged it into this branch.

✋ automatically generating the entries file
Possible, but we can hold off for now until we better understand the quirks of the build process.

[dac09]

Ready for review!

@Tobbe the smoke test in RSC is still going to fail - wanted you to see the failure first, before I change the test. I think it's ok, just renders the suspense comments.

[Tobbe]

the smoke test in RSC is still going to fail - wanted you to see the failure first, before I change the test. I think it's ok, just renders the suspense comments.

Thanks for highlighting this for me. I agree, this is ok. Just change to innerText instead of innerHTML and it should pass again 👍

[dac09]

Headsup ⚠️ Last round of changes actually rows us backwards:

• I've essentially disabled SSR for pages (in renderFromRscServer) - this is until we figure out how to render RSCs on first render.
• Note: OG Tags, etc. won't be rendered either, unless you use a routehook too

So while the build processes are integrated, the final result is not. Once you enable RSC you get:
✅ Client side rendering
❌ Server side rendering (only partially)
✅ Server component rendering after client has been hydrated

For streaming ssr:
✅ Client side rendering
✅ Full SSR
❌ Server component rendering