Bart Veneman

Maybe `calculateFromAstNode` or `calculateSelectorNode`, `calculateNode`? The return type is Specificity, so no real need to include that in the function name.

1 more way to improve this function is to allow our own csstree walker. Project Wallace is powered by CSSTree too, so we already have a walker function available, next...

Ah, sorry, misread the code: it doesn't use an AST walker, it just loops over some of the nodes 😬. So that already makes it pretty lightweight. The only dependency...

Thanks for chiming in! Adding another dependency is indeed not high on my list for a feature like this, so I'll see if/when CSSTree can give me a similar setup....

So what if we could represent specificity like this: `{ a: 1, b: 0, c: 0 }`? This would mean that we have a selector that has a single id-selector,...

Example breadcrumb implementation: https://codepen.io/bartveneman/pen/GRoooxa

Adding flexbox to concentric won't help? I think adding flexbox would be a good addition anyway. But I'd +1 a separate file for property sort order.

For what it's worth, using the scss-lint plugin in sublime text already gives some feedback on .sass files. Of course not all of it, but for me it's enough to...

use this: https://github.com/projectwallace/format-css/commit/bfd235ba78cf66fedc505a8daec415ef73b05445

beta.syntax.fm actually uses containers, so can be used for testing