email export: `--outDir` outside the project fails for `<Tailwind>` templates with "Cannot find module 'css-tree/dist/csstree.esm'" (since 6.8.0)
I maintainer di solito rispondono entro 1 giorno
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 76/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- node.js, react, typescript
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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
- Lingua principale
- TypeScript
- Stelle
- 20k
- Fork
- 1.1k
- Merge medio
- 2g 4h
- PR unite (30g)
- 80
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di resend/react-email
-
Heading: margin shortcut props (m, mt, mx, ...) produce invalid CSS for values with units such as "1.5rem" or "10px"Forse già presa @officialasishkumar l’ha presa 1 giorno fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 35/100
resend/react-email#3924 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
resend/react-email#3878 · 2 commenti · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno
-
Dependency DashboardApertadependencies
Difficoltà 5/5 Più di una settimana Idoneità per principianti 15/100
resend/react-email#746 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di resend/react-email
Issue simili
-
parity: scripting.net's net-http row fails on macOS with errno 61 where the BDS golden has 111ApertaBug Tests
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
JSPrismarine/JSPrismarine#3384 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
zingolabs/zingo-mobile#1951 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
Automattic/data-liberation-agent#2175 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
xdelmo/Portfolio-minimal#613 ·
I maintainer di solito rispondono entro 1 giorno
-
backend documentation low-priority Stellar Wave
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
Savitura/Savitools#611 · 1 commento ·
I maintainer di solito rispondono entro 6 giorni