react-server-dom-turbopack

/* This quickstart illustrates how a meta-framework *might* conceptually use * react-server-dom-turbopack. Application developers should NOT use this directly. * Instead, use a framework like Next.js that integrates React Server Components. */ // Conceptual server-side rendering setup (framework-level) import { renderToPipeableStream } from 'react-server-dom-turbopack/server'; async function serveReactServerComponent(req, res) { const Component = () => { // This would be a React Server Component in a real framework setup return <h1>Hello from a Server Component!</h1>; }; const { pipe } = renderToPipeableStream(<Component />); res.setHeader('Content-Type', 'text/x-component'); pipe(res); } // Conceptual client-side hydration (framework-level) import { createFromReadableStream } from 'react-server-dom-turbopack/client'; async function hydrateClientComponent() { const response = await fetch('/rsc-payload'); // Imagine fetching the RSC payload const stream = response.body; if (!stream) { throw new Error('Response body is not a readable stream.'); } const { default: ServerComponent } = createFromReadableStream(stream); // In a real framework, this 'ServerComponent' would be rendered into the DOM // using ReactDOM.createRoot().render(<ServerComponent />); // For this conceptual example, we'll just log its existence. console.log('Server component received and ready for hydration:', ServerComponent); } // Example usage simulation (not runnable as a standalone app) // serveReactServerComponent(mockRequest, mockResponse); // hydrateClientComponent(); console.log('This code illustrates framework-level integration and is not for direct use.');