Tailwind v4 Support

[mririgoyen]

Goals

To allow use of the Tailwind component utilizing the new, v4 CSS config method.

Background

Tailwind's new recommended configuration method is via a CSS file, not a JavaScript config file. It used to be possible to simply include the Tailwind JS file and pass it in as a prop on the Tailwind component. This is not possible using their new recommendation.

Proposal

It would be super convenient if there was a way for the Tailwind component to utilize the new CSS-based config so that a config object doesn't need to be manually created and kept in sync with master Tailwind CSS config.

[andrevandal]

please help!

[pietrobs]

Tailwind v4 Support, Please!

[vinnymac]

Is there any appetite for react-email to migrate from v3 to v4? The performance appears to be much better when compared to v3, although I am not sure if those wins would translate directly to this email sdk.

Regardless one of my applications that uses @react-email/[email protected] at scale would greatly benefit from any performance improvements. The wall time (see graph below) is very high when building an email dynamically in my application. We are sending a very large number of emails, and have been exploring ways to optimize our use of react-email and resend.