Stats doesn't work properly with CSS variables about cssstats

[lachlanjc]

Unfortunately I think ^ is correct. Nonetheless, maybe we could render whatever is defined on :root?

[bartveneman]

Custom properties are evaluated by the browser at 'runtime', meaning that var(--my-custom-property) could have different calculated values, based on the place it has in the document, the default/fallback value and probably some other cases I'm not thinking of at the moment.

CSSStats does not know about all this context, because all it analyzes is the raw CSS it encounters on a given page. It would be impossible to render the variables correctly based only on the CSS.

But perhaps there's something I'm missing here? 🤔

[lachlanjc]

Closed by #308! @johno

[johno]

Thanks for bubbling this up @lachlanjc!

The CSS AST has enough information for most custom property handling, though ofc it misses anything affected by a runtime since this tool works purely statically (by design).

v4 now contains a fix that should address 90% or so of variable/custom property usage. It still missed nested variables, but that's something for another day I think so I'm going to close this. Thanks all!