fix(render): Import renderAsync function

[michael-dickinson-sainsburys]

Fixes this error message when calling renderAsync function (#868):

✖ in ../node_modules/@react-email/components/node_modules/@react-email/render/dist/index.mjs 31:23-45
    export 'renderToReadableStream' (imported as 'renderToReadableStream') was not found in 'react-dom/server' (possible exports: renderToNodeStream, renderToPipeableStream, renderToStaticMarkup, renderToStaticNodeStream, renderToString, version)

[shellscape]

@michael-dickinson-sainsburys not getting that error on my end. what's the context under which this error occurred? bundling? tsc? which version, and which platform?

Here's a better fix that takes into account what the react docs have to say:

import react from 'react-dom/server';

const { renderToStaticMarkup } = react;
const renderToStream =
  // Note: only available in platforms that support WebStreams
  // https://react.dev/reference/react-dom/server/renderToString#alternatives
  react.renderToReadableStream ||
  // Note: only available in Node
  react.renderToPipeableStream;

export const renderToString = async (children: ReactNode) => {
  const stream = await renderToStream(children);

[gustavo-depaula]

@shellscape, I think this is solving this issue: #868

[shellscape]

Unfortunately it's not thorough enough to resolve the issue across several platforms.

[diegoholiveira]

Any news about this issue?

[shellscape]

@diegoholiveira I ended up forking the project to get around issues like these. 😬

[devrsi0n]

Hi @bukinoshita , could you help take a look at this PR? Thank you in advance.

[bukinoshita]

Yeah, we've been testing this. The canary.1 release is with this change, but it doesn't fix the issue

[gabrielmfern]

The error mentioned has been fixed in a better way and is already released, going to close this as it is not the optimal way