-
Notifications
You must be signed in to change notification settings - Fork 678
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Build failed #1497
Comments
Thinking this might be because by yarn modern's pnp. Here's an issue someone else also had #1422 (comment) |
@gabrielmfern getting the same issue, there are no pnp files in my project. react-email@2.1.4 |
following up, I had to add react and react-dom as direct dependencies to my package. the project is a |
Not sure what's happening but I have this error in a personal project, works in one computer and not in another. Also using pnpm workspaces, code in https://github.com/propsto/props.to/tree/auth-domain and by running in the root Also tried including |
@iantanwx From the comment I mentioned, the yarn files were not on their project but rather on their home:
From what you mention @leog,
I am pretty sure this is the same problem as said in the comment. Also, the repo you sent doesn't have the script nor does it have react-email installed 😅. |
@gabrielmfern notice I shared a repo with a particular branch |
I see it now, but no issues on my side: Here's a separate comment on an issue talking about this evanw/esbuild#2647 (comment) (we use esbuild internally, that's precisely why this fails now). Thinking you have ran |
Can't wait to go back to my other computer and find those bastard files braking my emal dev flow 😄 |
yeahp, found it at |
Describe the Bug
Getting errors when previewing out-of-the-box emails.
Which package is affected (leave empty if unsure)
create-email
Link to the code that reproduces this issue
To Reproduce
Follow the instructions here https://react.email/docs/getting-started/automatic-setup
Expected Behavior
Have out-of-the-box emails preview successfully as shown in docs.
What's your node version? (if relevant)
v18.18.2
The text was updated successfully, but these errors were encountered: