New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use browsers from new targets config #88
Comments
Also see: kimroen/ember-cli-autoprefixer#34 |
@mydea thanks for submitting this! Yeah, I think this is a great idea. After reading over the article and other repo you mentioned, I think it would make sense to add Does that sounds like what you had in mind? Is there anything I'm missing? Cheers, thanks! |
Yes, that sounds perfect! |
@mydea would you be able to help me test this? I have this ready on the branch |
Awesome, I tried it out with the branch, and it seemed to work just fine! |
@mydea thanks for the help! I've published this as V3.4.1, which should support using Please open a new issue if there are any bugs with this. Thanks! |
When using this addon together with e.g. 'autoprefixer', you currently configure autoprefixer like this:
Following the new possibilities as outlined here: http://rwjblue.com/2017/04/21/ember-cli-targets/, you can now have a
config/targets.js
file like this:It would be great if we could use that config if no browsers are set directly for autoprefixer (and possibly other plugins).
The text was updated successfully, but these errors were encountered: