CSSNano: A modular minifier based on the PostCSS ecosystem
1–10 of 10 posts
Re: CSSNano: A modular minifier based on the PostCSS ecosystem
#2[deleted]
Re: CSSNano: A modular minifier based on the PostCSS ecosystem
#3This 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.
Re: CSSNano: A modular minifier based on the PostCSS ecosystem
#4Similar : https://github.com/hail2u/node-csswring
Written with PostCSS too
Re: CSSNano: A modular minifier based on the PostCSS ecosystem
#5This 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...
Re: CSSNano: A modular minifier based on the PostCSS ecosystem
#6Some 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.
Re: CSSNano: A modular minifier based on the PostCSS ecosystem
#7Some 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.
Since v3.2.0 this is no longer done by default and can be enabled via the config object. The website should probably be updated to reflect this.
Re: CSSNano: A modular minifier based on the PostCSS ecosystem
#8This 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...
Exactly. Use PostCSS in conjunction with preprocessors.
Re: CSSNano: A modular minifier based on the PostCSS ecosystem
#9I 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 ?
Re: CSSNano: A modular minifier based on the PostCSS ecosystem
#10I 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 ?
I don't have a gzip benchmark for cssnano itself, but I know that the road to best compression is using both.