Max
Max
I just faced this issue. Then I waited a little, & then, while trying again after having prepared an issue & trying to double check the problem, issue was gone!
https://github.com/pascalduez/postcss-apply
Yep, should be something like v1.2.0 according to bower/semver spec
That's my point. CSS level 4 does not exist. CSS after 3 has been exploded into modules with their own level.
That's why this project have a "browsers" option: to disable the thing you don't need (like autoprefixer does).
For now it just avoid to run the plugins, but that might be an enhancement to not even download them (=> only npm install packages that are required by the...
Yes via the "features" option http://cssnext.io/usage/#features The only two options that will be kept after official migration to postcss-cssnext will be "browsers" and "features" :)
Stupid question: why don't you use rely on "node_modules" when available ?
For the usage I have in mind, I would not be interested to have reason conversion directly. It closes door to dynamic rendering that can adjust components during rendering. I...
Might be interesting.