Server side render a component (React.element) defining a static document into a string, the client rerenders the component (createRoot / render)
Server side render a component (React.element) defining a document into a markup string (contains a few differences on the output compared to the renderToString version). The client hydrates it with the same component (hydrateRoot)
Server side render into a stream. A comments page that loads without any additional client-side code and just Suspense + streaming the HTML
A client fetching a single react server component with createFromFetch
A single page to with server components and SSR (with hydration), client components to test all props serialisation, including React.element and Js.Promise. Also renders Js.String/Js.Date JavaScript-identical values on the server (UTF-16 string semantics, local-time date parsing).
A dummy implementation of a router (only a few queryStrings) as a single page app. Server components with SSR, client components and Suspense + React.use
The same demo as dummyRouterRSC but without SSR. It SSR the shell of the page (head, body, etc), but not the app itself.
A nested router with server components and SSR, client components and Suspense + React.use. It uses the same design as the dummyRouterRSC but with a more complex structure that can handle nested routes and dynamic segments.