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
Version 10 doesn’t work in PostCSS 7 #1359
Comments
Do not update Autoprefixer until it will release next major update. |
switching back to version 9 |
If Autoprefixer v10 isn't ready for the masses to use yet then it would be best not to make it the default download when people install using
You should publish a new v9 release and then publish a v10 release using
This means that by default users will install the stable v9 release. Users can then opt into the unstable v10 release using this command:
|
@Dan503 it is already ready for webpack users. Some users will always suffer because many environments needs a year to update PostCSS. Right now we have a clear error message |
autoprefixer version 10 breaks next.js on start. It clashes with next's postcss-loader, returning error - ./styles/index.css (./node_modules/next/node_modules/css-loader/dist/cjs.js??ref--5-oneOf-5-1!./node_modules/next/dist/compiled/postcss-loader??__nextjs_postcss!./styles/index.css)
Error: true is not a PostCSS plugin Rolling back to autoprefixer@9.8.6 resolved the issue. |
@DopamineDriven please vote for this issue to update PostCSS 8 in Nuxt.js vercel/next.js#17242 |
autoprefixer 10 doesnt work |
Closing this issue, since Autoprefixer 10 requires PostCSS 7. |
I also had problem with Autoprefixer v10, there were no build errors but it didn't add prefixes.
|
@x35a you will need the latest |
Thanks @ai |
PostCSS v8.1.1 with Autoprefixer v10.0.1 does not work for me. Error: Found in: Code: "use strict";
const postcss = require('postcss');
const unprefixed = postcss.vendor.unprefixed; // <--- HERE
// ... Example Code: const path = require('path')
const sass = require('node-sass')
const postcss = require('postcss')
const cssnano = require('cssnano')
const rtl = require('postcss-rtl')
const autoprefixer = require('autoprefixer')
const postCssCompiler = postcss([ autoprefixer ])
const postCssRtlCompiler = postcss([ rtl({}) ])
const nano = postcss([
cssnano({
preset: ['default', {
mergeLonghand: false,
convertValues: false,
cssDeclarationSorter: false,
reduceTransforms: false
}]
})
])
// ... |
@hawkeye64 |
@ai Now I feel less worthy. :( |
PostCSS does not work with autoprefixer v10 see postcss/autoprefixer#1359
As identified in this post: https://stackoverflow.com/a/64837198/1611058 Manually installing postcss and postcss-loader fixed the issue for me without having to downgrade Autoprefixer.
"devDependencies": {
"autoprefixer": "^10.0.2",
"postcss": "^8.1.7",
"postcss-loader": "^4.0.4"
} |
Since the release of v10, autoprefixer is now failing with a variety of errors.
My command is as follows:
npx postcss file.css --use autoprefixer --no-map --replace
Some errors say "[object, Object] is not a PostCSS plugin" (when using -u autoprefixer).
Without the "-u autoprefixer", the error is "You did not set any plugins, parser, or stringifier. Right now, PostCSS does nothing. Pick plugins for your case on https://www.postcss.parts/ and use them in postcss.config.js.". This is happening even if a postcss.config.js is present.
Removing the "--replace" resolves the issue, but adding "--output file2.css" results in the same error as above.
These issues occur after running "npm install -g --save-dev autoprefixer postcss".
Downgrading to v9 resolves the problem.
The text was updated successfully, but these errors were encountered: