Skip to content
← Back to activity

Solution skill

v3.3.0 is throwing an error

Version 2

Complete solution

Shows how to fix v3.3.0 is throwing an error. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Root cause (gabrielmfern, maintainer): @react-email/render 0.0.15 broke the react-dom/server import for runtimes where only the default export exists (Convex/V8, ESM bundlers).

Steps

  1. [vcapretz (maintainer)]: Released v4.0.1, which bumps the @react-email/render dependency to v1, closing the issue. Root cause (gabrielmfern, maintainer): @react-email/render 0.0.15 broke the react-dom/server import for runtimes where only the default export exists (Convex/V8, ESM bundlers). Interim workaround: force the canary build via package overrides - "resend": { "@react-email/render": "0.0.16-canary.0"} (npm overrides / yarn resolutions).

When to use

You are seeing this: Issue resend/resend-node#381 (closed, 9 comments): I saw that v3.3.0 was made available through npm even though there are no release notes here on GitHub. Use this skill when you run into "v3.3.0 is throwing an error".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: v3.3.0, next 14.2.4, react-emailrender 0.0.15, prev v0.0.12, Released v4.0.1, 0.0.16-canary.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Asked in gh:resend/resend-node#381 (https://github.com/resend/resend-node/issues/381): v3.3.0 is throwing an error. The issue report: Issue resend/resend-node#381 (closed, 9 comments): I saw that v3.3.0 was made available through npm even though there are no release notes here on GitHub.

It broke my email sending capability with next@14.2.4.

here's the error which goes back to @react-email/render@0.0.15 bumped from the prev v0.0.12

Error: Dynamic require of "stream" is not supported
    at file://[HOME]/...
    at file://[HOME]/...
    at Generator.next ([anonymous])
    at file://[HOME]/... The verified answer: [vcapretz (maintainer)]: Released v4.0.1, which bumps the @react-email/render dependency to v1, closing the issue. Root cause (gabrielmfern, maintainer): @react-email/render 0.0.15 broke the react-dom/server import for runtimes where only the default export exists (Convex/V8, ESM bundlers). Interim workaround: force the canary build via package overrides  -  `"resend": { "@react-email/render": "0.0.16-canary.0"}` (npm overrides / yarn resolutions).

By @issueatlas · Version 2 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_T5I0WWd7OCAQRAj1EcjvNA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">v3.3.0 is throwing an error <span>— Vectle</span></a>