-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
Tailwind CSS v4 support #513
Comments
@adamwathan Are there any syntax-related changes in Tailwind CSS v4 that I should be aware of that weren't mentioned in the announcement post or upgrade guide? |
I think the only syntax-ish changes are these:
I think that's everything 👍 |
@adamwathan awesome, thanks for the list! I wonder: Do you have some code in the Tailwind CSS codebase that checks whether variants are reorderable? E.g. in tailwind-merge sorts variants internally (between arbitrary variants) to allow better deduplication, but maybe it isn't feasible anymore to do that. |
@dcastil I think there is some stuff for that sort of thing here: Here's the tests which explain what it changes and doesn't change: |
This was addressed in release v3.0.0. |
Tailwind CSS v4 will be released next week: https://x.com/adamwathan/status/1879856208552845570.
I expect to add support for it a few days after the Tailwind CSS v4 release. Most probably it will be a new major tailwind-merge version with the only breaking change being that it supports Tailwind CSS v4 instead of v3.
Feel free to subscribe to this issue to get notified when support for Tailwind CSS v4 lands.
Some additional info in #468.
Changes to check
✅ Tailwind CSS v4 annnouncement
Tailwind CSS v4 annnouncement
✅ Upgrade guide
Upgrade guide
✅ Utility schemas
✅ Syntax changes
#513 (comment)
&
Issues discovered
shadow
class missing in v4 docs tailwindlabs/tailwindcss.com#1985flex
API table tailwindlabs/tailwindcss.com#2002The text was updated successfully, but these errors were encountered: