Define multiple browser targets for a single build

[mm2ha]

First of all, I am not sure if this is a question for ember-cli-babel or ember-cli.

I am wondering if there is any way to accomplish having ember build generate 2 different JS and CSS sets of files based on 2 different target browsers definition. The first package would have regular names and the second could have "-legacy" appended for example.

The use case for this is the following - we would like to serve non-transpiled source code to browsers that support it, and regular transpiled code to all others.

Any suggestions on how this could be accomplished are greatly appreciated!

[astronomersiva]

We were also trying to do this and had some success recently. If you use ember-cli-deploy and the lightning strategy, you will have to generate two builds(one transpiled and another non-transpiled using ENV variables) and make the build label of the second build as ${first_build_label}-legacy. When serving the build, detect the browser and send the index.html of ${latest_build_label}-legacy.

[BryanCrotaz]

I'm doing this but I'm having issues with addons. The addon babel config seems to be separate from the app config. So when I build the app for legacy browsers (eg transforming async to promises) the addons aren't transpiled.

How did you solve this?