-
Notifications
You must be signed in to change notification settings - Fork 31
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 2 compatibility? #35
Comments
Hello, The issue comes from this file:
Since Tailwind 2, the Unfortunately I didn't have time to work on this plugin since a few weeks because of my work, and even though I still plan on upgrading it, it won't be before at least mid-january. If you can confirm that this is the only issue with Tailwind 2, I can release an update quick enough though. |
Thanks for the details. Yes that appears to be the main blocker to upgrading right now. The classes are being generated as expected, just with the wrong names. |
Hey, I tagged a new beta version which should bring Tailwind 2 compatibility. Can you let me know if it works for you? |
Thanks for the update - classes are now being generated as expected! Unfortunately it appears that PurgeCSS is not working as expected with tailwindcss-theming. Using default Tailwind 2 purge config all themes are getting stripped out. Any ideas on that one? |
Can you share your config? The plugin really just edits your Make sure you have followed the whole documentation on purge: https://tailwindcss.com/docs/optimizing-for-production |
Yeah good point - I had an issue in the purge config. Looks good now! |
First of all thanks for the amazing work on this plugin, it really came at the right time for our project!
I'm currently trying to upgrade from tailwind 1.9.6 tailwind 2.0.2. After completing the upgrade guide I noticed the themes were not loading correctly. Looking at the generated css it seems all the color class names are being suffixed with
-default
now. For example the color namedon-background
will generatetext-on-background-default
.This issue is happening in
2.4.3
andv3.0.0-beta.2
.Any ideas on how we complete the upgrade?
The text was updated successfully, but these errors were encountered: