-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
@headlessui/tailwindcss incompatible to tailwindcss v4 #3633
Comments
It’s frustrating to have completed an entire TailwindCSS V4 migration only to discover that neither Headless UI nor the Typography plugin are compatible with TailwindCSS V4. It would be considerate to the users to include a clear notice about this—ideally, right at the top of the upgrade guide. Adding such a note would be simple and would save users a lot of time and frustration. 🙏🏼 |
Hey @topical! Thanks for reporting. You're right the version range in the
@mirhamasala Sorry for the frustration you are having :( I'm curious if you can explain more about the kind of compatibility issues you are referring to regarding the Typography plugin? The npm version dependency range is updated to work with v4 already on that plugin, so I'm surprised you ran into issues there. |
We just published an updated version of |
Thank you, @philipp-spiess.
I encountered similar migration issues as those described in this thread, particularly around customizing the plugin’s theme. In the end, I followed this advice, and it worked. However, having clear official migration documentation would have been really helpful. |
What package within Headless UI are you using?
@headlessui/tailwindcss and @headlessui/vue
What version of that package are you using?
@headlessui/tailwindcss v0.2.1 and @headlessui/vue v1.7.23
What browser are you using?
Any
Reproduction URL
Just try to install tailwindcss v4 and @headlessui/tailwindcss:
Describe your issue
@headlessui/tailwindcss is (officially) incompatible to tailwindcss v4
The text was updated successfully, but these errors were encountered: