<p dir="auto">Hi,</p>
<p dir="auto">I am in the process of migrating our codebase to React 0.14.x. During this I encountered a problem, because of the fact that our client side uses <code class="notranslate">React.renderToStaticMarkup</code> to render React components and passing the results around as strings (I know, not ideal, but given what our codebase was previously, this is sadly needed for us in some cases).</p>
<p dir="auto">However, given my understanding of the structural changes with <code class="notranslate">react</code> and <code class="notranslate">react-dom</code> packages, as I can tell, I am not supposed to simply call <code class="notranslate">React.renderToStaticMarkup</code> any more, and the API is not accessible from the <code class="notranslate">react-dom</code> package. I do not use webpack (yet!), so at the moment using <code class="notranslate">react-dom/server</code> is not appropriate for me.</p>
<p dir="auto">What is the supported way (if any?) of calling <code class="notranslate">React.renderToStaticMarkup</code> in the browser, using the pre-built packages?</p>
<p dir="auto">We have some corner cases within our client-side application which requires <code class="notranslate">React.renderToString</code> functionality. In 0.14, this has been deprecated in favor of <code class="notranslate">ReactDOMServer.renderToString</code>. Unfortunately, the bower distribution does not include a way to reference <code class="notranslate">ReactDOMServer</code>.</p>