-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Migration to Tailwind v4? #19
Comments
https://x.com/adamwathan/status/1764393609246261496:
The new "CSS configuration" looks remarkably easy to use so I imagine it won't be too difficult to convert it to that. I'm sure they'll have good documentation on migrating plugins as well. |
Can't say until they've figured how they want to go about it. Seems like everything will be CSS based, I assume that there'll be some magic to translate |
Tailwind v4 beta is out with migration docs. Now the plugin's theme variable works, but custom classes are broken. Any idea to adapt the new version? |
So far the following seems to work in a Tailwind v4 CSS file:
I recognize it's basically reassigning all the color variables a second time, but it seems to make the classes work and it is responsive to changing the class between the various Catppuccin flavors. |
Tailwind doesn't even provide proper/complete documentation on plugins and themes yet, so I'd be patient until v4 fully releases before we can look into upgrading. |
Tailwind v4 has been released. https://tailwindcss.com/blog/tailwindcss-v4 |
Based on a fix by @brianseidman on catppuccin#19
Hoping to take a stab at this, soon™ |
I just saw this tweet by Adam Wathan about the early Tailwind v4 alpha:
https://twitter.com/adamwathan/status/1764383146559017048
In it, it's mentioned that the Tailwind config file (
tailwind.config.mjs
) is no longer necessary.How will this affect the Catppuccin plugin?
The text was updated successfully, but these errors were encountered: