Max Thirouin

Are you interested to get access to this repo ? I'm not using Compass or Sass for several month, and this project for more than a year. # For now...

safe option doesn't exist yet (in the version used by cssnext). Try using postcss + postcss-cssnext + cssnano directly (this will be the recommended version in a week or two...

cssnext-loader will be deprecated, soon, you should consider using postcss-loader + postcss-cssnext plugin.

I will keep that issue open so people will see it if they got an issue. Will close if someone fix it or when npm package will be deprecated.

This looks like an autoprefixer bug.

We should disable the option `messages.console` and instead use a custom plugin to emit warnings using [email protected]

cssnext "just" inline import statement, so it's a normal behavior. The problem is, if we handle the imports in a different way (via webpack instead of inlining), we might loose...

http://cssnext.io/usage/#features in webpack config ``` js module.exports = { entry: "path/to/entry", // ... cssnext: { features: { customProperties: { variables: {mainColor: "#f00"} } } } } ```

yes it seems this should works. I guess tests are wrong :/ I opened an issue for that https://github.com/postcss/postcss-custom-media/issues/11

I don't really use sourcemap, so not sure what might cause the issue. That being said, if you want someone to fix the bug you are reporting, you can help...