next build fails: Cannot get final name for export 'encodeXML' (resend + react-email)

TL;DR

For "./nodemodules/html-to-text/lib/html-to-text.mjs + 24 modules / Cannot get final name for export 'encodeXML' of ./nodemodules/entities/lib/": resend fixed this in v2.0.1-canary.0 (PR #259): upgrade the resend package and rebuild, which multiple reporters confirmed resolves the build.

./node_modules/html-to-text/lib/html-to-text.mjs + 24 modules / Cannot get final name for export 'encodeXML' of ./node_modules/entities/lib/esm/index.js

Steps

1. Resend fixed this in v2.0.1-canary.0 (PR #259): upgrade the resend package and rebuild, which multiple reporters confirmed resolves the build. Workaround for the broken versions: pre-render the component with renderAsync from @react-email/render and pass the result as the html property instead of react:

const html = await renderAsync(MagicLinkEmail({ url, host }));
await resend.emails.send({ from, to, subject, html });

2. Note: one reporter found the bug reappeared in 2.1.0-canary.0, so pin the working canary if you stay on the canary channel.

When to use

You are seeing this: On Next.js 14 with resend 2.0.0/2.0.0-canary.2, passing a React email component to the react property of resend.emails.send breaks next build with:./node\_modules/html-to-text/lib/html-to-text.mjs + 24 modules / Cannot get final name for export 'encodeXML'... Use this skill when you run into "next build fails: Cannot get final name for export 'encodeXML' (resend + react-email)".

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: resend 2.0.0, 2.0.0 2.0.0-canary.2, v2.0.1-canary.0, 2.1.0-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.

Question asked in the thread: On Next.js 14 with resend 2.0.0/2.0.0-canary.2, passing a React email component to the react property of resend.emails.send breaks next build with: ./node_modules/html-to-text/lib/html-to-text.mjs + 24 modules / Cannot get final name for export 'encodeXML' of ./node_modules/entities/lib/esm/index.js. It works fine in local dev; only the production build fails. Multiple reporters reproduced the same failure on resend 2.0.0.

Verified answer: Resend fixed this in v2.0.1-canary.0 (PR #259): upgrade the resend package and rebuild, which multiple reporters confirmed resolves the build. Workaround for the broken versions: pre-render the component with renderAsync from @react-email/render and pass the result as the html property instead of react:

const html = await renderAsync(MagicLinkEmail({ url, host }));
await resend.emails.send({ from, to, subject, html });

Note: one reporter found the bug reappeared in 2.1.0-canary.0, so pin the working canary if you stay on the canary channel. Source: https://github.com/resend/resend-node/issues/256

Thread: https://vectle.com/threads/thr_Zg-Qfp6SLfTqvwUPZvF22A