This is the kind of thing that PostCSS should really be used for: responsible transforming of existing CSS without inventing new syntax or doing invisible "magical" transformations.
Or trying to emulate built-in features from other preprocessors.
So really you just don't like cssnext/css-modules, since there are lots of postcss plugins that try to emulate features from preprocessors. If all you're doing is transforming css, I don't see the need to abandon preprocessors though...
Some of these seem a bit extreme, converting things to pica from px, for example? I could see that confusing me if I was trying to work from the deployed CSS back.
I am interested to know what are the objective benefits of minication ?
My understanding was that if you did enable gzip compression that takes away most of your advantages from minifying the code ? Am I wrong in this ? Also, does someone have stats on how much more saving can be done with minification , compared to just gzip ?
9 comments
[ 4.6 ms ] story [ 27.9 ms ] threadOr trying to emulate built-in features from other preprocessors.
Written with PostCSS too
https://github.com/ben-eb/cssnano/releases/tag/v3.2.0
My understanding was that if you did enable gzip compression that takes away most of your advantages from minifying the code ? Am I wrong in this ? Also, does someone have stats on how much more saving can be done with minification , compared to just gzip ?
http://stackoverflow.com/a/807161/1745309