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
targets.js #47
Comments
Also, what do we do about a conditional list // taken from targets.js
if (isCI || isProduction) {
browsers.push('last 2 Edge versions');
browsers.push('ie 11');
} |
Anybody got any input on this? |
Hi @amk221, I also brought this up in #45 (comment) Sounds like Martin is definitely open to README improvements, and possibly to re-adding support |
...so this means I end up with vendor prefixes for 'last 2 Edge versions' and 'ie 11' in my development builds. Prior to version 1 of ember-cli-autoprefixer, this wasn't the case. The point of the conditional in targets.js is for quicker build times in development. Can we get some insight into why this change was made? |
@amk221 Can the logic you need be moved to |
Not sure how that would work? A Edit: you changed the comment - oh I see - it could. But it doesn’t really round the issue off very well. |
See |
Actually I see the issue. This wrapper library should feed the browser list in targets.js. One sec. Let me push a PR up. |
Seems good. I'm questioning why this was removed in the first place :) |
@amk221 @snewcomer TL:DR -> I'm not against re-adding support for It was removed to bring the usage in line with how the underlying autoprefixer library expected to receive config. There's a conversation worth having about how these things should be handled in an Ember specific context. For example, the documentation for configuring autoprefixer expects the configuration to be read from different files This presents some possibility of confusion for someone reading the documentation for autoprefixer. When I did the upgrade I referenced the advice in the autoprefixer docs
I can see the value of re-using the There's an argument to be made that this should be a major version bump. Anyone using the 1.x version would have their current configuration living in |
I considered the Node 10 a major. The fact that Is your desire to pass in two different browser lists to Babel and autoprefixer? I haven't come across an app where these two configurations were different (yet :) ). |
I'm not concerned about moving back to |
Agreed. I think we can muster up something...order of importance -
What do you think? |
Sounds reasonable |
Ok, thanks for the info. I suppose the inverse might be nice... I mean, that ember-cli didn't use targets.js, but just consumed .browserlistrc. But that aside, I'm happy to go with whatever. Keeping it how it is now, or going with your new solution. |
|
My understanding was that ember-cli-autoprefixer took the list of browsers from
targets.js
. As of 1 beta, the suggestion is to use.browserlistrc
.I quite liked not having to maintain the list of browsers in multiple places.
What is the plan going forward? Is the intention that ember-cli will read from
.browserlistrc
too?The text was updated successfully, but these errors were encountered: