Implement Support For Preprocessors? about grunt-uncss

[addyosmani]

I think that this is something possible, but wouldn't be on the block until after a stable release of the project. Right now there are currently still a number of selectors (arguably more complex ones) where we break on and I'd love for us to optimize those first and then move on to these interesting other use-cases. Does that make sense? :)

[nicdaCosta]

100%, thank you :)

I didn't think at this stage it would be possible as I am sure there were still a few cases that would have needed to have been resolved, as you mentioned. It would make sense to get a stable release first before diverging into other use cases.

I guess I was more curious to see if something like that would be possible in the future as I was chatting with some teams about implementing something like this and one of the main aspects that kept coming up was preprocessor support.

Anyway, thanks for the feedback. Will keep a close eye on this :)

[koriolis]

Source maps are a possibility or take advantage of the debug mode of SASS (to give an example I'm more familiar with) that bind the compiled css line to the SCSS source files
Either way implementing this with preprocessors will be huge for those who use frameworks like bootstrap and foundation on their pre-compiled versions.

[addyosmani]

Btw, I published an example of how I feel uncss should be used in a preprocessor workflow: https://github.com/addyosmani/grunt-uncss-sass-example tl;dr - execute it after you've compiled your Sass/Less near the end of your build process, pass in the relevant pages and rewire where your pages are pointing to to reference the newly tidied stylesheet.