Parcel CSS: A new CSS parser, compiler, and minifier

Re:Parcel CSS: A new CSS parser, compiler, and minifier by zelphirkalt on Wednesday January 12, 2022 @07:33PM (#29915112)

That's really nice, but to me still sounds like the wrong way to go. Instead of reducing something that is too much, that which is too much should not have been added in the first place. We are doing work here, removing, what we have previously added.

I wonder how much ineffective styling still remains after "tree shaking". I guess the fancy tree shaking is out of luck, if we add unnecessary styling to elements, which are indeed used. It seems a really hard problem to solve automatically, to transform CSS in a way, that takes care of redundancies and unnecessary styling, while still maintaining the readability, which well crafted CSS can have.

[ Parent | on HN ]

Re:Parcel CSS: A new CSS parser, compiler, and minifier by dmitriid on Thursday January 13, 2022 @02:03AM (#29917677)

> that which is too much should not have been added in the first place.

The problem is, with CSS you don't know if you've added too much. As the project evolves, and code and styles change there's literally no way of knowing if a certain CSS rule is still in use Well, except regexp'ing the whole project looking for matches.

[ Parent | on HN ]

Re:Parcel CSS: A new CSS parser, compiler, and minifier by selcuka on Friday January 14, 2022 @12:38AM (#29930981)

> regexp'ing the whole project looking for matches

That's basically what these tree-shaking tools do.

[ Parent | on HN ]