4 ms·
This is pretty cool! > Are the current CSS minifiers correct? > I handle crashing minifiers, as well as ones that loop forever. It could actually be useful t
by vmarsy 10y ago
This is pretty cool!
> Are the current CSS minifiers correct?
> I handle crashing minifiers, as well as ones that loop forever.
It could actually be useful to know the exact css before running the minifier who crashed/got stuck. One could check with a css validator if this is correct css in the first place (if not, one of the previous minifier screwed up) , and if so, inform the minifier's maintainers of their tool crashing with this particular valid input.
- simcop2387 10y ago> It could actually be useful to know the exact css before running the minifier who crashed/got stuck. I was actually thinking this could be used to speed up computation a bit too. If you're going to add a set of minifiers to the end of the chain, caching the intermediate results (really just the last one) would let you avoid reprocessing from scratch each time you need to do cssnano | cssnano | csso | *, I don't know if it does this now but the description didn't talk about it either. That'd let you look at the chain and find where a mistake propagated from.