So you start making a brand new CSS analyzer and you’re all fired up to get to work on it. You find a CSS parser, transform the AST into some kind of statistics and there you go: your own pretty little analyzer! But… in this case I made a mistake very soon in the process: choosing Reworkcss over PostCSS, because PostCSS seemed so much harder to work with. Of course I was wrong.
- Let Reworkcss transform the CSS into an AST;
- Analyze the AST, including making the AST simpler in some cases; For example, Reworkcss creates an AST that reflects the actual tree structure of the CSS file, so nested Media Queries could appear, nested rules and many more complex structures. This is ok if you want to do some in-depth analysis of things, but for a quick analysis it’s easier to have a flat structure, like PostCSS does. In the case of using Reworkcss we have to do some recursion at a couple of places to make sure that we don’t miss out on some (edge) cases.
- Unit tests for analysis; Only test the output of the whole application, without intermediate steps for the parser for example. If something in the parser fails, it’ll fail in the eventual output. That’s not the right way to approach it.
Let PostCSS create a flat AST; And flat means that there’s no need to worry about nesting or other complex structures. When asking for all Media Queries, it returns all Media Queries, regardless of the document structure. That’s exactly what we need.
Transform the AST a tiny bit into something a little more suitable for analyzing; By creating an intermediate layer for the AST, we’re able to write tests for it and we’re making it easier to switch between parsers, because they will all be turned into simple arrays of strings of tiny objects.
Run tests for the analyzable AST;
Analyze the CSS; Run the analysis on the simple arrays and objects created in step 2.
Run tests for the analysis;
PostCSS is actually easier to work with than Reworkcss because of the ease of which you can get all rules, instead of having to go through the whole document yourself. It pays off to split even a relatively small application like this one into multiple layers to increase testability and maintainability. Have fun using Project Wallace CSS Analyzer!