driver-server

import {createElement, Component, render} from 'rax'; import ServerDriver from 'driver-server'; import {isNode} from 'universal-env'; class Example extends Component { render() { return ( <div> <img width="560" height="560" src="https://img.alicdn.com/tps/TB1z.55OFXXXXcLXXXXXXXXXXXX-560-560.jpg" alt="Example Image" /> </div> ); } } // Render the Rax component, specifying ServerDriver for Node.js environments // In a real application, you would capture the output and send it as HTML. const serverRenderResult = render(<Example />, null, { driver: isNode ? ServerDriver : null }); if (isNode) { console.log('Server-rendered HTML output:'); // In a typical SSR setup, this output would be sent to the client as the initial HTML. // The exact method to get the string might vary depending on Rax version, but render() handles it. // For simplicity, we assume render() directly returns a string in server context here. // You might need to check Rax's documentation for specific server-side output retrieval. // For illustration, assuming serverRenderResult holds the rendered content. // This exact output format of `render` in server context needs to be confirmed with Rax docs. // Rax's render for SSR usually directly outputs HTML to a stream or returns it. // The provided example shows `render(<Example />, null, { driver: ServerDriver })` // which implies ServerDriver intercepts the rendering and provides server-specific output. // Without more context on `render`'s server-side return, we'll demonstrate basic usage. // A common pattern is `ReactDOMServer.renderToString(element)` in React, for Rax it's part of the render function. console.log(serverRenderResult); // Placeholder, actual output retrieval might differ. } else { console.log('This code path is for browser rendering, not active in this quickstart.'); }