The confusion here is because webpack and broccoli are completely different things.
Broccoli is a tree builder, and that might not even be the right phrase to use. It’s basically virtual-dom for the file system. It’s not an asset bundler, nor a build pipeline. Ember-cli is a build pipeline that uses broccoli to assemble the things it needs to operate on. As one step of this build, it might use rollup or webpack or something else to operate on assets.
Webpack is an asset bundler that confuses itself for a build pipeline. It happens to do a couple of things well, but it’s been a huge failure in larger projects. Angular-cli chose to move to it for poor reasons that they aren’t even sure of. I’m also not surprised, ember-cli has an amazing plan for bundling in the works, but angular-cli probably jumped the gun here for a nearsighted win because despite forking ember-cli they showed little interest in being part of the community and angular2 launch was approaching.
Last time I checked, with ember-cli you need to add app.import line to ember-cli-build.js which exposes globals.
This does not expose a global, it merely adds it into your pipeline. If the module it’s importing is a global, then yes, it will add a global, but your use of it should still be to use