Open devklepacki opened 4 weeks ago
Have the same issue. Downgrading to "@react-email/components": "0.0.15"
fixed it for me.
Have the same issue. Downgrading to
"@react-email/components": "0.0.15"
fixed it for me.
Same here, but had the issue with "@react-email/components": "0.0.15"
too. On 0.0.14
it's working for me though.
This should be fixed under the latest canaries, for both @react-email/components
and @react-email/tailwind
. No need to downgrade here.
See https://github.com/resend/react-email/issues/1391#issuecomment-2035304838.
There were also a few other issues created after that original #1391 was closed, and even though I closed them as not planned, others kept popping up, so I'm going to keep this one open for anyone else to find. Even though this is still a duplicate, thank you, @devklepacki, for making it detailed and making a reproduction regardless of it already being fixed, people like you make open-source fun!
@gabrielmfern I've got no idea how I didn't find that older issue! Oh, maybe the default search filter was set to open issues... Meh. Anyway, confirmed that the canary version seems to be working. Thank you!
For me @react-email/tailwind@0.0.16-canary.1
worked, but @react-email/tailwind@0.0.16
didn't.
@poeck Yeah, I had to compromise there since we needed a new stable release urgently to fix the issues with peer dependencies, so the changes from canary weren't published. I should tune these versions out properly in the coming weeks. Probably making a new latest release with those.
If I'm still unsure of the stability of the changes in canary, I might make another canary release like 0.0.17-canary.x
with the new peer dependencies.
I'm on @react-email/components@0.0.17
and react-email@2.1.2
and the <Heading>
is completely missing from development and production emails.
Not sure how long this has been going on but it's super weird.
I'm changing <Heading>
to <Text>
and it will show. That's my short term fix.
@mfts After #1459 I will release the canaries again and that should be cleared up for now. Will close the issue and let you all know once this is released under a stable version.
Also, see my comment above to understand why it seems like there was a regression from canary to latest.
Released a new canary for @react-email/tailwind
that should be working with this. It is also on the latest canary for @react-email/components
.
Can confirm. I was having exactly this issue and these versions fix it
"dependencies": {
"react": "^18.2.0",
"@react-email/components": "0.0.18-canary.0",
"@react-email/tailwind": "0.0.17-canary.0",
"react-email": "2.1.3-canary.2"
},
Describe the Bug
Heading
component is not rendering when it's inside aTailwind
component. I was building a new email and was fighting withHeading
not displaying (not rendering in DOM at all). Once I've removed theTailwind
component wrapping my template theHeading
appeared. The same happens with newly created project usingyarn create email
.Join Enigma on Vercel
heading visible right under the logoTailwind
component is removed, theHeading
appearsWhich package is affected (leave empty if unsure)
@react-email/heading, @react-email/tailwind
Link to the code that reproduces this issue
https://github.com/devklepacki/react-email-reproduction
To Reproduce
yarn create email
, install dependencies and run itHeading
visible right under the logoExpected Behavior
Heading contents should be shown when used inside Tailwind component
What's your node version? (if relevant)
v20.11.0