email export: `--outDir` outside the project fails for `<Tailwind>` templates with "Cannot find module 'css-tree/dist/csstree.esm'" (since 6.8.0)
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 76/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- node.js, react, typescript
Research direction
Start at the email export CLI implementation and the change in #3643 that made the Tailwind path import css-tree/dist/csstree.esm. Trace how the export bundle is written and how its dependencies are resolved when --outDir is outside the project. Reproduce with the supplied Tailwind template and external output directory; done when it creates welcome.html and exits successfully, while default output still works.
Written by the indexing model from the issue text.
Description
What versions are you using? (if relevant)
react-email 6.11.13 (latest), react and react-dom 19.3.1, npm 11.16.0, macOS. It works on 6.7.0 and fails on 6.8.0, 6.9.0, 6.10.0, 6.11.12 and 6.11.13, so it looks like a regression in 6.8.0. The npm canary tag is 6.0.0-canary.2, older than latest, so I couldn't test a newer canary.
Describe the Bug
I wanted to export my templates straight into a sibling backend folder with email export --outDir ../backend/templates. For any template that uses <Tailwind>, it fails with:
Error: Error: Cannot find module 'css-tree/dist/csstree.esm'
Require stack:
- /path/to/backend/templates/welcome.cjs
It exits 1, writes no .html, and leaves welcome.cjs (about 35k lines) in the output folder. The same template exports fine to the default out. A template without <Tailwind> exports fine to the same outside folder. An outDir under $TMPDIR or $HOME fails the same way, with or without --plainText or --pretty. Running it with NODE_PATH=$PWD/node_modules works, and so does exporting to another folder inside an npm workspaces repo where css-tree is hoisted to the root.
It looks like the bundle keeps css-tree external and is then required from the outDir, and since 6.8.0 (#3643) the Tailwind code imports css-tree/dist/csstree.esm instead of inlining css-tree.
What is affected (leave empty if unsure)
CLI (email export)
Link to the code that reproduces this issue
No repo: the whole reproduction is one file and two commands, below.
To Reproduce
In an empty folder my-emails, next to an empty folder backend:
npm install react-email react react-dom -E
emails/welcome.tsx:
import { Html, Tailwind, Text } from "react-email";
export default function Welcome() {
return (
<Html>
<Tailwind>
<Text className="text-blue-600">Hello</Text>
</Tailwind>
</Html>
);
}
npx email export --outDir ../backend/templates
Result: the error above, exit code 1, and only ../backend/templates/welcome.cjs. npx email export with the default out gives out/welcome.html.
Expected Behavior
../backend/templates/welcome.html and exit code 0. The CLI page documents --outDir as "Change the output directory." and lists "When the email content must be processed by a backend in a language other than JavaScript." as a reason to use email export, so exporting into a backend folder seemed like the intended use.
What's your node version? (if relevant)
v26.3.0
- Dominant language
- TypeScript
- Stars
- 20k
- Forks
- 1.1k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 80
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from resend/react-email
-
Heading: margin shortcut props (m, mt, mx, ...) produce invalid CSS for values with units such as "1.5rem" or "10px"Possibly taken @officialasishkumar claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
resend/react-email#3924 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
resend/react-email#3878 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Dependency DashboardOpendependencies
Difficulty 5/5 Over a week Newbie friendliness 15/100
resend/react-email#746 ·
Maintainers usually reply within 1 day
All issues in resend/react-email
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
code-yeongyu/senpi#7139 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
lingdojo/kana-dojo#34395 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
bug status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mastra-ai/mastra#31093 · 1 comment ·
Maintainers usually reply within 1 day
-
area:web p2 product:business triage:active type:bug
Difficulty 1/5 Under an hour Newbie friendliness 89/100
cuadrao-ai/argus#2328 ·
Maintainers usually reply within 1 day
-
bug frontend good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
nikhilb2/simple_invoicing#907 ·