youtube-stats-card VS css-analyzer

If the answer to the above question is yes, then this article is valuable for you. Recently I created a project which dynamically generates YouTube Stats Card for the youtube channels and videos. These cards will give an aesthetic look on your Github profile readme and the repo readmes as compared to the normal youtube URL.

The core CSS Analyzer (please star it on GitHub!) has seen 10 releases this year in total: Support for analyzing Embedded Content in CSS, like base64 encoded fonts or images; Lots of browserhacks are now analyzed, ranging from at-rules and selectors to properties and values; The relatively new @layer at-rule is now analyzed Total bundle size went down a lot because CSSTree now supports tree shaking! Lots of performance improvements and less overall memory usage, despite adding more and more features.

My goal is to work on a complete list and implement all these into Project Wallace's analyzer, so we can all inspect the things we've made. Here's a list of things I'm considering to add to CSS complexity:

The idea about this site didn’t come over the night. I remember how excited I was when I saw The Project Wallace for the first time. I thought it was so cool, and I should somehow use it in my favor. The problem was I couldn’t figure out how.

CSS Analyzer — Generate an analysis for a string of CSS.