mjs build uses require

[kentcdodds]

Describe the Bug

The module at @react-email/render/dist/index.mjs attempts to use require which is not supported in a native ESM environment (it's an mjs file so it's native ESM).

As a result, when calling renderAsync, you get the following error:

Error: Dynamic require of "stream" is not supported

This is because require is not defined in a module using native ESM.

Which package is affected (leave empty if unsure)

@react-email/render

Link to the code that reproduces this issue

epicweb-dev/epic-stack#749

To Reproduce

Attempt to use renderAsync with the mjs build.

Expected Behavior

It renders properly without error.

What's your node version? (if relevant)

v20.13.0

[gabrielmfern]

This should be fixed by #1491, once we release a canary I'll let you know

[pjamrozowicz]

@gabrielmfern any estimates for the new release date? This error is currently blocking me 😢

[gabrielmfern]

Just released the fix for this under canary. It should be working under @react-email/render@0.0.16-canary.0 and @react-email/components@0.0.20-canary.0.

[YannHulot]

I am still getting this error even though I updated the packages to the canary versions.
I can't really share a repo with the issue though since the code is proprietary.

[YannHulot]

Just to add to my previous message. The error happens when I try to render an email in an API route on Nextjs.

Its a very simple route. I tried changing the runtime to edge and node and still get the same issue.

The code looks like this:

 const html = await renderAsync(LoginWithMagicLink({ loginUrl: url }), {
      pretty: true,
    })

NextJs version: 14.2.4 with pages router
react-email/render: 0.0.16-canary.0
react-email/components: 0.0.20-canary.0

[HananoshikaYomaru]

@YannHulot I am the same problem. I am using Astro with API route. Local works fine but deployment failed. Are you using Vercel as deployment platform? Just curious is it possible that the problem happens on Vercel?