Buggy with ember.js about grunt-uncss HOT 7 CLOSED

As per the readme, the project doesn't yet support detection of styles dynamically added via JavaScript. Is this the problem you're running into at the moment? If not, it may be that our parser is breaking due to something in your templates. Once you've clarified I'll be able to comment further :)

from grunt-uncss.

I think parser is breaking because of something in templates. Because some styles get loaded knowing that it is only defined in .hbs files. I'm thinking this has something to do with bindings? {{bind-attr class="my-class"}} or {{view App.TextView classNameBindings="class"}}

If thats the case would it be possible to have a variable to set in uncss to give it alternative names or aliases?

from grunt-uncss.

@addyosmani does that also mean it does not work yet with single page apps with pushStates or "#!" ?

from grunt-uncss.

bump :)

from grunt-uncss.

It should work fine with single page apps and apps using templating for the views. We're going to try putting together a sample to demonstrate this. Btw, where possible I recommend running uncss as a post-processing step once you've compiled templates and anything else your build needs to do. Attempting to run it against raw template files won't work as we need to be able to run the rendered markup straight-up in Phantom.

from grunt-uncss.

Just to clarify: so, point uncss at the URLs where your final views/templates are being consumed.

from grunt-uncss.

Thanks for clarifying this 👍

from grunt-uncss.