lib/broccoli/ember-modules-app

[ember-cli]

lib/broccoli/ember-modules-app

[nathanhammond]

@Turbo87 We clearly require an interoperability story here. However that should not be a primary consideration at the beginning of this effort. I want for our first step to be, "given what we know from the years of experience we have in this problem space, this solution is closest to our ideal." Once we know what our ideal is, we can work backwards to identify how best to migrate our users to that solution.

For those following along more casually let me emphasize again that there will be a compatibility story and a migration story. This is integral to the commitments we make in maintaining Ember CLI and the community. The approach we take to building this does not in any way change our support promises.

[Turbo87]

Add backwards compatibility in as a last step (focus on the future use case).

can you clarify that? not sure how to understand this...

[stefanpenner]

It is worth saying, this is largely a spike to figure out what we want. We will then work back and figure out how to support it. Not that we will implement ship then try and figure out compatibility.

[danmcclain]

I started working on the new resolver (mostly around determining which module and export we need to look up based on the internal module manifest) here: https://github.com/danmcclain/ember-resolver/blob/new-resolver/tests/unit/new-resolver-test.js

Few things I need to still cover on it, but wanted to surface what I have