-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
v3.0.0 does not work #37
Comments
@tldrd0117 would it be possible for you to test this? |
i tested postcss-load-plugins module.exports = {
plugins: [require('postcss-plugin'), require('postcss-plugin-a')],
}
//or
module.exports (ctx)=> {
plugins: [require('postcss-plugin'), require('postcss-plugin-a')],
}
//or
module.exports (ctx)=> {
plugins: ['postcss-plugin', 'postcss-plugin-a'],
} next.js postcss config only use {string} module.exports = {
plugins: ['postcss-plugin', 'postcss-plugin-a'],
} |
and you can use same config file “.postcssrc.json" in root folder {
"plugins": {
"postcss-preset-env":{
"autoprefixer": {}
},
...postcss plugins
}
} |
@u3u can you generate a new Next.js app, add only the amount of changes to reproduce the issue and push it to a github repository? I'd like to take a look and see what's going on. |
I have the same issue. Just found that on my side it happens because the child process exits with one error:
This happens because next 9 default postcss support uses a non standard postcss config schema: https://err.sh/next.js/postcss-shape. So if you want to skip the default next 9 postcss support and use this plugin you have to use this shape:
module.exports = {
plugins: {
'postcss-flexbugs-fixes': {},
'postcss-preset-env': {
autoprefixer: {
flexbox: 'no-2009',
},
stage: 3,
features: {
'custom-properties': false,
},
},
},
} From: https://nextjs.org/docs/advanced-features/customizing-postcss-config. Possible the only fix for styled-jsx-plugin-postcss@3 from this is to throw an exception when |
this can happen with invalid postcss config Fix giuseppeg#37
this can happen with invalid postcss config Fix giuseppeg#37
this can happen with invalid postcss config Fix giuseppeg#37
This can happen with invalid postcss config Fixes #37 * fix error handling for css syntax error * add message about Next.js 9 non standard postcss config
I just published |
I tested the version using v2.x and it worked
Maybe related to #35 commit
The text was updated successfully, but these errors were encountered: