Skip to content

Tailwind CSS Vesion 3 Breaking Change #3

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

Closed
goxmedia opened this issue Dec 10, 2021 · 6 comments
Closed

Tailwind CSS Vesion 3 Breaking Change #3

goxmedia opened this issue Dec 10, 2021 · 6 comments

Comments

@goxmedia
Copy link

goxmedia commented Dec 10, 2021

Upon upgrade to Tailwind CSS v.3.0, the following import is now breaking within tailwind.config.js: require('tailwindcss-fluid-type');. Package.json has been updated to Tailwind v3.0.

Demo also breaks when chaning the Tailwind version to 3.0: https://play.tailwindcss.com/3LDf3gzbhb

Side Note: Thanks for your awesome work on this plugin. We absolutely love it.

@davidhellmann
Copy link
Owner

Hey, thank you!
It works on your local dev stuff not or just in the playground?
Maybe it's not ready to use plugins for now.
Found this issues: https://github.com/tailwindlabs/play.tailwindcss.com/issues/102

Did the update on my boilerplate yesterday and works fine:
davidhellmann/craftcms-baukasten@15de9ee

Maybe you can share your a bit more details.
Did you update the plugin to the latest version 1.3.2?

@goxmedia
Copy link
Author

Hi David,

Thanks for your reply. Appears to be related to the same issue as tailwindlabs/play.tailwindcss.com#102, but not sure.

Yes, issue occurs on local dev and the playground.

Screen Shot 2021-12-11 at 8 26 23 AM

Screen Shot 2021-12-11 at 8 30 09 AM

I also upgraded your plugin to v1.3.2. I also see that Tailwind has just been updated to v3.0.1, so I'm going to instal that and see if it resolves this issue. Thanks.

@goxmedia
Copy link
Author

Same issue after upgrading Tailwind to v3.0.1. Might be a Tailwind thing like you said.

@davidhellmann
Copy link
Owner

Looks like this is a TS issue?
Maybe a project config / vs code config thing?
Found this: tailwindlabs/tailwindcss-forms#18 (comment)

@goxmedia
Copy link
Author

Thanks. I'll give that a try. Never had to do that before but based upon the link you shared but I'll give it a shot. Not sure why the playground would be affected though.

@davidhellmann
Copy link
Owner

I close this for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants