fix(tailwind): React.forwardRef components not working

[nzben]

We were finding that some components in our UI library were not being correctly rendered.

On investigation it appears that in a couple of places in the Tailwind component, there's a check to see if the child is a functional component. For example:

react-email/packages/tailwind/src/tailwind.tsx

Line 93 in e72d089

if (typeof modifiedElement.type === "function") {

When using React.forwardRef, the child appears as an object with a render function, which was failing this test.

Unsure if there's a better option, but this PR expands the check to also see if the child has a render function and uses that instead of the child itself.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-email-demo	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 2, 2024 8:08pm

[vercel]

@nzben is attempting to deploy a commit to the resend Team on Vercel.

A member of the Team first needs to authorize it.

[gabrielmfern]

Can you also run pnpm format on the root of the code in the fork's branch?

[gabrielmfern]

@nzben Could you check the "Allow edits and access to secrets by mantainers" option? This is so that I can fix the conflicts here.

Wanted to get this one merged.

[nzben]

@gabrielmfern weirdly, I don't see that option :(

I'll try to merge upstream and fix the conflict.

[gabrielmfern]

@nzben Weird that it doesn't appear even though GitHub mentions it 🤔

Would be awesome if you could fix the conflicts. This PR should actually fix #1391 as well, so really wanted to get this merged.

[gabrielmfern]

@nzben You can also try reopening the PR here, from the same branch and fork, with the option checked so that I can fix the conflicts.

[nzben]

Should be good to go now @gabrielmfern

[gabrielmfern]

Thank you so much @nzben. Just merged it, will release in a few. Loved this PR, feel free to open other ones if you find the need to 🥰