6 ms·
CSSnano
- replete 2y agoLightningCSS[0] is better and faster, unless something has changed. https://lightningcss.dev/ https://lightningcss.dev/
- fallingsquirrel 2y agoWe tried LightningCSS and it gave buggy output for us because it doesn't keep track of property ordering. I wouldn't use it until that's fixed. https://github.com/parcel-bundler/lightningcss/issues/547 https://github.com/parcel-bundler/lightningcss/issues/547 https://github.com/parcel-bundler/lightningcss/issues/572 https://github.com/parcel-bundler/lightningcss/issues/572
- replete 2y agoUnfortunate to see these issues open for over a year, especially as previous versions did not do this. Thanks for the heads up
- GaggiX 2y agoJust seeing how bad the site renders on my phone I wouldn't trust it.
- ycombinatrix 2y agoLooks fine on my phone.
- GaggiX 2y agoOn my phone it has some extreme borders and in many lines it can only fit one single word.
- fenomas 2y agoTFA and GP are CSS minimizers - nothing to do with styles per se.
- muhrizqiardi 2y agoIt works fine for me--but I wonder if it has to do with the exessive shadow/glow effect?
- replete 2y agoI've used it on a few projects successfully. The property ordering thing mentioned in other comments though is good to be aware of. It's not difficult to switch out for css nano if that is the case. The important feature for me was being able to target a browserlist string and flatten CSS nesting
- Inviz 2y agoWhy keep background-position, if background overrides it anyway?
- troupo 2y agoCan't say exactly why, but I had this suggested by IDEA (?) as well. Could be because background is a kitchen-sink of everything there is in a background including several different DSLs for gradients and such. So it makes sense to keep just background-position if there's a simpler background: the browser will spend less time processing it. Whether that is measurable is a different story :)
- Inviz 2y agoYeah though within context of a single rule keeping that prop is pure overhead
- seu 2y agoThis is all great, but while the internet is filled with auto-playing videos and invokes to external scripts from google, meta, amazon and who knows where, the example on this page is about saving... 148 bytes? Does minifying CSS really make a big difference, in the end? I'm guessing that a page with a serious CSS payload (say, over 100k) already has more serious weight problem elsewhere.
- tosh 2y agoThe main problem with CSS is that it is "render blocking". If you want the user to see stuff sooner you have to make the CSS smaller and/or serve it faster (e.g. inline it to avoid another request).
- agos 2y agohow sooner will I see the stuff if I use this tool?
- tosh 2y agoI haven't measured yet but my guess would be that on current devices 99% of the CSS size saving matters for making the transfer of the CSS faster over the network (and that the speed up in constructing the CSS Object Model is negligible). => Users with low bandwidth and/or flakey connection benefit Happy to learn otherwise though!
- agos 2y agonever mind a "big" difference, I would be surprised if it made a "measurable" difference
- hawski 2y agoCSS is a high level language used very often as a low level one. The styling doesn't use any "cascading" and everything is repeated all the time. In this context minifying can make a difference. But either way it is not among my favorites.
- 2y ago
- weinzierl 2y agoIs there a tool that can remove unused CSS while considering static HTML? What I have in mind is a tool that I throw a CSS file and a bunch of static HTML files at, it will try to apply each CSS rule to the HTML like a browser would and remove all the rules that don't apply. I don't expect it to ascertain if a rule had visible effects. I also don't expect it to consider JavaScript. Just plain CSS and static HTML. It doesn't look to me like CSSnano or LighteningCSS could do that.
- csande17 2y agohttps://purgecss.com/ https://purgecss.com/ does this, kind of -- it used to be recommended by Tailwind back when Tailwind shipped a giant zip-bomb stylesheet of every possible property/value combination by default. I don't think it does the more complicated browser-like analysis you mention, though; it might just check whether class names appear in your HTML using a regex search. The AMP WordPress plugin also does something like this IIRC (to try and fit stylesheets into AMP's size limit) but the tooling for it might be written in PHP.
- alberth 2y agoHow do you remove the unused CSS? https://purifycss.online/ https://purifycss.online/ Above is a nice online version of Purify. But it just seems to minimize the CSS, and doesn’t delete the unused CSS.
- stigok 2y agoThis would work nicely with static HTML, indeed. But once you have some JavaScript i.e. dynamic HTML, it won't work reliably anymore. Worse, it might even give you a list of manually curated CSS properties to "allow list".
- merb 2y agothis is incorrect. the only thing that does not work is generating the css class like: var x = 'hase-'; var t = x + 'danger' which is an antipattern. (it can even happen inside java, c#, whatever language you use and it is still an antipattern)
- lofaszvanitt 2y agoPeople need more things that can be discovered. Everyone reinvents the wheel rn.
- a-french-anon 2y agoEh, even on this example, most of the gains come from simply removing the comments (something that can easily be done with `cpp -E -P <in.css >out_cpp.css` or regexps since CSS doesn't allow comment nesting) on most UNIXes. Here's a more complete result adding brotli and the aforementioned cpp version: $ gdu -b *.css *.css.gz *.css.br | awk '{if (NR % 3 == 1) {ref = $1; print} else print $0, "(" $1 - ref ")"}' 623 in.css 197 out.css (-426) 355 out_cpp.css (-268) 345 in.css.gz 185 out.css.gz (-160) 235 out_cpp.css.gz (-110) 284 in.css.br 141 out.css.br (-143) 177 out_cpp.css.br (-107)
- sionisrecur 2y agocpp as in a C preprocesor? That's a neat trick. I guess it removes what looks like /* comments */ and leaves the rest alone?
- no_wizard 2y agocssnano has had some complicated ownership turnover[0], I'm glad to see someone took the mantle again though. I do find that CSSO[1] with structural optimizations can be more effective still, perhaps that will be less true overtime though. I think once lightning CSS is more stable (in particular, some bugs are addressed around ordering) it will be the clear winner in this space though. [0]: https://github.com/cssnano/cssnano/issues/833 https://github.com/cssnano/cssnano/issues/833 [1]: https://github.com/css/csso https://github.com/css/csso