Running compatibility transforms for new d3 packages

[buschtoens]

d3/d3-array#80 (comment):

Yes, I’m starting to adopt more recent ES features in D3 modules. [...]

d3 is starting to use ES features, which are not natively supported in browsers like IE11. Since all packages are just run through the amd transform, this means that unsupported syntax, like arrow functions, makes it into the production build.

I guess this means, that ember-d3 should run the treeForVendor through ember-cli-babel with transforms based on the host project's targets.js?

[ivanvanderbyl]

@buschtoens thanks for letting us know. This will require some refactoring, we avoided this in the past because it added a considerable compile time cost during development. This could be overcome, just needs a PR ;)