-
Notifications
You must be signed in to change notification settings - Fork 64
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
PostCSS 8 support #161
Comments
I got the following error just now. I'm guessing it's related to this issue.
My // ...
const postcss = require("gulp-postcss");
const prefix = require("autoprefixer");
const cssnano = require("cssnano");
function buildCSS() {
return src("src/scss/main.scss")
.pipe(sass({ includePaths: ["node_modules/"] }).on("error", sass.logError))
.pipe(purgecss({ content: ["src/**/*.html"] }))
.pipe(postcss([prefix, cssnano]))
.pipe(dest("_site/"));
} Everything works fine if I remove Autoprefixer. What can I do to fix this please? Thank you. |
Just published a new version of gulp-postcss. |
@w0rm I stll get the issue below even after upgrading
Am I missing something here? |
@dippas yeah, you need |
@w0rm sorry my mistake I had updated to v9 and not v8 (i was confusing |
@dippas ah, I see. Since this error is coming from the PostCSS itself, maybe one of your plugins is not upgraded yet? |
I have every dependency updated, when running
So I think I missing something basic here. Do I have to run |
@dippas yes! PostCSS should be installed as a peer dependency now: https://github.com/postcss/gulp-postcss#install |
Yes after running |
Fixes "[object Object] is not a PostCSS plugin" Ref: postcss/gulp-postcss#161
Fixes "[object Object] is not a PostCSS plugin" error - ref: postcss/gulp-postcss#161 - fixes: #74
Fixes "[object Object] is not a PostCSS plugin" error - ref: postcss/gulp-postcss#161 - fixes: #74
PostCSS 8.0 changelog
postcss
topeerDependencies
postcss
versionThe text was updated successfully, but these errors were encountered: