LESS/SASS/Stylus etc preprocess support

[paazmaya]

Any change of getting some of those preprocessors supporter, or more specifically, the format they use to be supported?

So that running

stylestats path/to/stylesheet.less

would output similar results with additional mixin usage statistics.

[Anenth]

+1

[just-boris]

+1. I want to exclude bootstrap styles from stats. To do this, I need to analyze my LESS sources without bootstrap.

[eduardojmatos]

+1

[christianboyle]

+1

[1000ch]

Do you want statistics of SASS (not compiled) ?

[christianboyle]

Compiled, ideally. And LESS please, since a lot of people are using Bootstrap with this tool, to isolate their override stylesheet.

[paazmaya]

In the description of this issue, I meant unprocessed LESS and sorts, so the efficiency of the used mixins and variables could be revealed.
The compiled version statistics do not add much to having LESS compiled first manually and then running stats on the resulting CSS.

[1000ch]

We think that CSS statistics should be collected from CSS ,
so we don't have a plan now to analyze files which are not compiled.

[eduardojmatos]

I think that, initially, the compiled version is a great step! In the future, the unprocessed could be awesome :)

[paazmaya]

I agree with the positive points!

[phun-ky]

+1

[wvddrss]

+1, I used compass stat to generate stats, and send it to a graphite server to visualize it, but since libsass is faster, I've stopped using it.

[t32k]

It's related to #140
As mentioned above, we think that CSS statistics should be collected from CSS.
However, It might be possible to support SCSS files if we move to PostCSS.