-
Notifications
You must be signed in to change notification settings - Fork 47
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
css-modulesify / autoprefixer postcss version mismatch? #49
Comments
@zaim can you please give us a link to the repo so we can see the bug in action? |
You mean my project's repo? It's a personal project, not yet open sourced. What kind of information would you need? Maybe I can post my package.json and Makefile in a gist? |
Yes a gist would be good thanks. Just something so that we can reproduce the bug, and understand all of the factors at play. |
autoprefixer@latest (6.0.3) uses [email protected] @zaim you can fix this issue by downgrading your autoprefixer ( @joshwnj you may want to consider updating css-modules-loader-core and subsequently css-modulesify to use [email protected] so that css-modulesify can work with the latest postcss plugins. |
This and many other bugs will get fixed by #47 |
@zaim can you please confirm whether this issue is fixed now that we're on postcss v5? |
I'm running css-modulesify 0.16.1 with autoprefixer 6.3.1. I don't see the error. |
Closing as this is most likely resolved now |
I got this error while trying to use css-modulesify with autoprefixer: Your current PostCSS version is 4.1.16, but autoprefixer uses 5.0.8. Perhaps this is the source of the error below.
Not sure if its something wrong with my browserify command incantation, or what.
Full output below:
The text was updated successfully, but these errors were encountered: