-
Notifications
You must be signed in to change notification settings - Fork 12k
Unknown error from PostCSS plugin. Your current PostCSS version is 6.0.14, but autoprefixer uses 5.2.18. #9029
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
Comments
Thanks for reporting this issue. However, this issue is a duplicate of an existing issue #9020. Please subscribe to that issue for future updates. |
Issue #9020 is closed, but not corrected, as a this issue. |
@monoflash looks like the fix is coming in #9023 . |
@monoflash a fix has been merged (#9023) and it will be part of the next release. |
How to I can fix for project? Install @angular/cli@latest ? |
Good question, I've tried:
But they all give I assume we'll get a new release this week though. EDIT: Even with that github version—silly me on version numbers BTW, you haven't changed it in master's package.json—I am still getting the same error as OP. 😢 |
Can anyone give some recommendations how to fix this until the new release? |
Installing |
Ouch, it's still present in
|
@SamuelMarks Can you run the following |
Thanks for your response @clydin in the other thread. My global and local @angular/cli versions are both 1.6.4, but the issue persists. Here is my result from
|
@aarongranade can you put that in a code block (triple backticks)? It's hard to read. The key here is the location of cssnano's dependency on autoprefixer@6.7.7. My guess is the wrong one is being picked up. Removing node modules and the package lock and then installing is an option to reset the package hierarchy. Also if you are comfortable using a beta release, |
Please see the updated
|
It's a transitive dependency so the CLI doesn't have control over it. CLI 1.7 removes the actual use of the cssnano. It will still be present but unused. Note that 1.7 is currently in beta, however. |
Update your angular/cli to latest version. |
I corrected this error by removing bootstrap 4 from the assets folder |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Versions
Repro steps
"../node_modules/font-awesome/css/font-awesome.css",
"../node_modules/bootstrap/dist/css/bootstrap.css",
"styles.css"]
or
add to src/styles.css import tags:
@import "~font-awesome/css/font-awesome.css";
@import "~bootstrap/dist/css/bootstrap.css";
Observed behavior (Result)
The text was updated successfully, but these errors were encountered: