> It is designed to avoid redundant or similar css between files
See also CSS Stats, https://cssstats.com/, and atomic/functional/utility CSS libraries more generally which are designed exactly to eliminate as much redundant CSS as possible.
I mean, when you start deleting css because you think it's redundant.
Not a comment on the tool itself, just the nature of css and it's emergent complexity. It's very difficult to refactor large css codebase, especially in an automated or part-automated fashion.
Except that Parcel is a parser, deduper, transformer [autoprefixer, future-CSS-to-current-convertor] and minifier.
And that, in turn, is based on CSSNano [although it is a complete rewrite in Rust], IIRC.
Can someone confirm that I understand correctly, and if so, how does this compare to Parcel? To CSSNano or PurgeCSS?