Open ryngonzalez opened 9 years ago
HI @ryngonzalez do you have a repo somewhere that we can get a better look at what's going on?
@ryngonzalez have you tried loading cssnext
first, then autoprefixer
, and finally the others?
cssnext
includes the plugin postcss-import which recommends loading it as the first plugin in the list.
Using postcss-cssnext
instead of cssnext
works wonders for me!
@izeau where'd you put postcss-cssnext
in your case? Can't see to get it working with --after
. Also, is it working for globally defined CSS variables by any chance?
It's working alright for me in the cli:
browserify -t babelify -p [css-modulesify --after postcss-cssnext -o main.css] -o bundle.js src/index.js
Here's a boilerplate that supports cssnext with this library. https://github.com/pixelass/npm-boilerplate
Here's a react/redux boilerplate with more config: https://github.com/pixelass/redux-react-boilerplate
Both work out of the box and need no config. I simply added it in the after
array.
I've tried with a bunch of configurations, and none seem to be working:
1. In
--use
declaration2. In
--after
declaration3. Required and used in
--use
declaration4. Required and used in
--after
declaration5. Required and used in
--use
declaration, initialized with options6. Required and used in
--after
declaration, initialized with optionsAm I just missing fundamental, or is there some for of issue with how we're adding additional PostCSS plugins to the css-modulesify pipeline?