css-analyzer
css-analyzer copied to clipboard
projectwallace
Analytics for CSS
We already support complexity for selectors, but could extend this to add value, property, declaration and atrule complexities. This could also clear the way for having a 'total complexity' for...
Though not being used a lot, I could get rid of some classes and use a factory method + local scope and see how that affects perf. https://twitter.com/_developit/status/1437432231413305345?t=D6J-muJFyCd-V5c9ZYdSEQ Not important,...
CSS can be in an `@layer` atrule, or not. It would be interesting how many rules/selectors/declarations are within layers and how many aren't. Maybe even report it in a way...
[This article](https://www.tandfonline.com/doi/full/10.1080/24701475.2022.2055274) by @wilsonderren did a great job analyzing CSS Zen Garden's CSS over the years, but they had to rely on manual analysis for determining some browserhacks. Support for...
They're stripped off, see https://www.stefanjudis.com/today-i-learned/the-surprising-behavior-of-important-css-custom-properties/ (thnx @stefanjudis), just like `!important` within a `@keyframe` is ignored.
I've never used it and it's one of the bottlenecks because of the `.sort()`
I can think of two major use cases where I think it's most useful to no longer include substrings as aprt of the result: - Showing the reports on https://www.projectwallace.com/analyze-css...
There's a couple of issues that can be resolved once we put in place an updated method of walking our AST: we need to keep track more of how rules...
This package has had some breaking changes in the past and it's hard to compare results from previous analysis with the current ones, for example using [css-analyzer-diff](https://github.com/bartveneman/css-analyzer-diff). This library should...