Closed ef4 closed 8 years ago
This is awesome
I'm in favor of this change. Other approaches to do things like this include running your own processing step and then shoving the result into the vendor
tree. This dramatically improves that story.
My only hesitations are small:
define
and wrapping it in another IIFEs (though @krisselden can speak to that far better than I can; I'm cargo-culting based upon conversations overheard).Note that I'm in favor even with those hesitations.
@nathanhammond can you elaborate on "may make it harder to support some build time tooling for rollup-like behavior"? I don't fully understand that part.
Perhaps you're concerned that my implementation is hiding the real module inside an extra layer? The API doesn't wed us to that behavior -- I think the API leaves us free to alter the implementation.
@ef4 this looks great, three things:
@ef4 friendly ping
@stefanpenner I pushed some edits that address your questions, except for
this AMD isn't really a full tree of AMD rather a single file. We should be sure to document this.
AFAIK, app.import
already doesn't do trees, so that is not specific to this issue. Plus I really don't know what it would mean to import a tree of anonymous AMD -- I don't think that's a well-defined thing (how could the modules in the tree find each other if they're really still anonymous?).
I also changed the proposed API based on discussion in https://github.com/ember-cli/ember-cli/pull/5976 so that we reserve API-space for future transformations, which can eventually become pluggable.
@ef4 this has been in PFC for some time, did the core team reach a consensus that I missed or did we drop the ball?
If so, I do feel good about this change. Should we maybe give core until this friday to object, then we ship?
this has survived PFC
Rendered
Related to https://github.com/ember-cli/ember-cli/pull/5976