Skip to content
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

Closed
zaim opened this issue Oct 4, 2015 · 8 comments
Closed

css-modulesify / autoprefixer postcss version mismatch? #49

zaim opened this issue Oct 4, 2015 · 8 comments

Comments

@zaim
Copy link

zaim commented Oct 4, 2015

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:

./node_modules/.bin/browserify -x moment -x react -x react-dom -x tcomb -x whatwg-fetch --debug -p [css-modulesify -o public/css/main.css --after autoprefixer --json app/styles/index.json] index.js | ./no
de_modules/.bin/exorcist public/js/bundle.js.map > public/js/bundle.js
Your current PostCSS version is 4.1.16, but autoprefixer uses 5.0.8. Perhaps this is the source of the error below.
TypeError: css.walkAtRules is not a function while parsing file: [path]/ui/app/components/styles/Progress.css
    at Processor.remove ([path]/ui/node_modules/autoprefixer/lib/processor.js:103:11)
    at plugin ([path]/ui/node_modules/autoprefixer/lib/autoprefixer.js:49:28)
    at LazyResult.run ([path]/ui/node_modules/css-modulesify/node_modules/css-modules-loader-core/node_modules/postcss/lib/lazy-result.js:197:24)
    at [path]/ui/node_modules/css-modulesify/node_modules/css-modules-loader-core/node_modules/postcss/lib/lazy-result.js:110:37
    at LazyResult.asyncTick ([path]/ui/node_modules/css-modulesify/node_modules/css-modules-loader-core/node_modules/postcss/lib/lazy-result.js:124:15)
    at [path]/ui/node_modules/css-modulesify/node_modules/css-modules-loader-core/node_modules/postcss/lib/lazy-result.js:122:27
    at LazyResult.asyncTick ([path]/ui/node_modules/css-modulesify/node_modules/css-modules-loader-core/node_modules/postcss/lib/lazy-result.js:124:15)
    at [path]/ui/node_modules/css-modulesify/node_modules/css-modules-loader-core/node_modules/postcss/lib/lazy-result.js:122:27
    at LazyResult.asyncTick ([path]/ui/node_modules/css-modulesify/node_modules/css-modules-loader-core/node_modules/postcss/lib/lazy-result.js:124:15)
    at [path]/ui/node_modules/css-modulesify/node_modules/css-modules-loader-core/node_modules/postcss/lib/lazy-result.js:122:27
@joshwnj
Copy link
Member

joshwnj commented Oct 4, 2015

@zaim can you please give us a link to the repo so we can see the bug in action?

@zaim
Copy link
Author

zaim commented Oct 5, 2015

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?

@joshwnj
Copy link
Member

joshwnj commented Oct 5, 2015

Yes a gist would be good thanks. Just something so that we can reproduce the bug, and understand all of the factors at play.

@themitchy
Copy link

autoprefixer@latest (6.0.3) uses [email protected]
css-modulesify@latest (0.9.0) uses [email protected] (via [email protected])

@zaim you can fix this issue by downgrading your autoprefixer (npm i --save-dev [email protected]). Using the older package isn't ideal but that's how I'm getting around this for now.

@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.

@themitchy
Copy link

This and many other bugs will get fixed by #47

@joshwnj
Copy link
Member

joshwnj commented Nov 19, 2015

@zaim can you please confirm whether this issue is fixed now that we're on postcss v5?

@huan086
Copy link

huan086 commented Jan 27, 2016

I'm running css-modulesify 0.16.1 with autoprefixer 6.3.1. I don't see the error.

@joshwnj
Copy link
Member

joshwnj commented Mar 24, 2016

Closing as this is most likely resolved now

@joshwnj joshwnj closed this as completed Mar 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants