-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Compatibility with PostCSS 8 #2396
Comments
Additionally, an error such as |
Just updated my dependencies and everything works fine like before. Here an excerpt from my
Probably it's relate to the node version? I'm working with |
Yep everything should just work, just need to be on PostCSS ^8.0.2 as there was a bug that broke things before that. You'll see a little deprecation warning but we can't do anything about that until Tailwind 2.0. I need to co-ordinate with some other framework authors and find out about their plans for PostCSS 8 support as well though before going all in. |
Sorry to say everything just doesn't work with PostCSS 8. I upgraded then downgraded my PostCSS plugins. The problem at #2426 is also PostCSS 8. Version 3.0.0 of postcss-scss plugin is using PostCSS 8. Keeping this issue open might be helpful for others. |
Sorry I don’t understand, what’s the actual Tailwind issue? If there’s an issue with postcss-scss it feels like that belongs in their repo rather than ours? If there’s an actual Tailwind issue we’ll fix it but currently there are no Tailwind issues related to PostCSS 8 as far as I’m aware. |
Unfortunately I cannot get Tailwindcss work with PostCSS 8. I maybe missing something (pretty late here and I'm exhausted) so I created a test repo so you can reproduce the issue. You can just follow the steps in the readme. Thanks! |
Yep looks like PostCSS 8.0.7 broke Tailwind again. Works with PostCSS 8.0.2-8.0.6. Will investigate, thanks. |
Here is the issue to track on PostCSS: |
Opened a PR that fixes the issue in PostCSS: postcss/postcss#1422 |
Fixed, update to PostCSS 8.0.8 👍 Thanks for the report. |
I don't know if I'm doing it wrong, but it still doesn't work with this repro: mkdir test && cd test
npm init -y
npm i -D tailwindcss postcss postcss-cli
npx tailwindcss init
npx postcss styles.css -o build.css styles.css: @tailwind base;
@tailwind components;
@tailwind utilities; postcss.config.js: 'use strict';
module.exports = {
plugins: [
require('tailwindcss'),
],
}; Error:
It seems like there's a mix of PostCSS 8 (installed at the root level) and PostCSS 7 (installed and used by |
I can also confirm that I have the same error @targos is getting, in the test repo I provided above, after updating PostCSS to 8.0.8. |
Working on it, another PostCSS bug. |
Any update @adamwathan? |
Everything should be working now, if you have an issue please start a new issue 👍🏻 |
This solved the issue for me: https://tailwindcss.com/docs/installation#post-css-7-compatibility-build |
As you probably know, PostCSS 8 was released a few days ago. It would be great if you could make Tailwind CSS compatible with the latest version. The creators of the project have even released this migration guide.
The text was updated successfully, but these errors were encountered: