-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
Error: [object Object] is not a PostCSS plugin #1358
Comments
Same here:
My /* eslint-env node */
module.exports = {
plugins: [
require('autoprefixer'),
require('cssnano')({
preset: ['advanced', {
autoprefixer: false,
discardComments: {
removeAll: true
}
}]
})
]
} |
Same as above, but with a
|
Did you update to Autoprefixer 10? It do not work with old PostCSS 7 and require PostCSS 8. Wait a little until |
@ai yeah, I'm using |
@evanleck you have another problem because |
I added |
Does this PR solves the |
@m4thieulavoie Yeap, Gulp users needs to wait before updating to PostCSS 8 plugins |
had Then I read the changelog which mentions so I |
Not working for me. I use postcss through parcel-bundler and configured it via module.exports = {
plugins: [require('autoprefixer'), require('cssnano')],
}; which resolves in I think parcel has to act here - or autoprefixer respectively. |
Just so you know, I have the same
Here's a example of my webpack.mix.js file if you want to reproduce the issue: mix.sass('resources/sass/app.scss', 'public/css')
.options({
postCss: [
require('autoprefixer'),
tailwindcss('./tailwind.config.js'),
],
}); I'm guessing we need to wait a Laravel Mix update? |
Hello, I have the same error using CRA and Webpack. My package.json "devDependencies": {
"autoprefixer": "^10.0.0",
"postcss-cli": "^7.1.2",
"tailwindcss": "^1.8.10"
} The postcss.config.js module.exports = {
plugins: [
require("tailwindcss")("./tailwind.config.js"),
require("autoprefixer"),
],
}; The error TypeError: Invalid PostCSS Plugin found at: plugins[1] |
Same here. What a mess today in the world with CI/CD environments! 😄 |
PostCSS 7.0.33 was released with a better error instead of Unfortunately, solving |
@ai since this issue is closed now, is there another place where we can track the problem so we know when we can upgrade autoprefixer to v10 once the issue is resolved? |
@evanleck you can track the issue in your PostCSS. For instance, postcss/gulp-postcss#161 |
Type: Addition ➕ The same problem for PostStylus after upgrading AutoPrefixer to 10.0. Example configuration. Thanks. |
@Kristinita can you create an issue in PostStylus about migration PostCSS 8. |
Type: Reply 💬 @ai, yes, but I’m not sure I will get any feedback from PostStylus maintainers:
Type: Question ❓ @seaneking, excuse me, is any chance, that PostStylus development will continue? Unfortunately, currently, PostStylus doesn’t support the latest Autoprefixer version. Thanks. |
Hey @Kristinita, I've long moved on from Stylus and PostCSS, so I'm not actively maintaining poststylus. But feel free to submit a PR to support whatever's missing and I'll happily merge it. |
Type: Reply 💬 @seaneking, OK, I created pull request; please review it. And please don’t forget to push the new PostStylus version to the npm if you approve my pull request. Thanks. |
I started having this issue after upgrading |
@billyromano report an issue in |
I also met the problem of:
and postcss.config.js:
and webpack:
hope that's helpful. |
- Seems postcss/autoprefixer#1358 is fixed
For grunt, |
|
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"
} |
I just happened to setup a new workstation, installed some tools to process SASS files and called something like
npm i -g node-sass postcss postcss-cli clean-css-cli autoprefixer browserslist
on the command line.I tried to prefix a css files using a statement like
postcss expanded.css -u autoprefixer -o prefixed.css --no-map
and got errorError: [object Object] is not a PostCSS plugin
I downgraded to
autoprefixer@9
and the error went away.I see version 10 had just been pushed. Is there an issue?
The text was updated successfully, but these errors were encountered: