Tailwind v4.0 has been officially released! 🎉

[andymerskin]

Woop! Looks like v4.0 is officially available now. This repo's been a little quiet for several months now, but Twin.Macro has ~60K weekly downloads — good usage still.

Are there plans to start supporting v4.0 in the near future? My team would like to keep using Twin (because we can't live without it!), but if there's no plans to keep it updated, we may start migrating away so we can start benefiting from Tailwind 4's features.

Thanks!

Site: https://tailwindcss.com/
X post: https://x.com/adamwathan/status/1882219476600635677

[ben-rogerson]

Hi Andy, great to hear from you!

Since the beta, I've made a few attemps to provide Tailwind v4 support but I've been having trouble hooking into their internal functions since their rewrite. Currently twin leans on a few vital functions from Tailwind in order to provide much of the same functionality however, the new codebase doesn't surface those same functions.
I'm aiming to give it another shot, but I'm not feeling too positive about arriving on a good solution.

I'd recommend migrating to Tailwind regardless as you're very likely see performance gains due to shifting away from css-in-js but I'm well aware of the time involved in this (I'm experiencing it right now at my day job).

I know this is probably not what you'd like to hear - but I'd rather be transparent with the upgrade issues and challenges Twin is facing here.

[therealgilles]

Curious if the Tailwind team would be responsive to adding access to the internal functions you need.

[andymerskin]

Sounds challenging for sure. Hopefully the Tailwind team would be open to this ⬆️