require.moduleId

[stefanpenner]

// app/foo
import require from 'require';
require.moduleId // => app/foo

[stefanpenner]

released as v4.5.0 🎉

[Turbo87]

@stefanpenner ember-cli/ember-cli-shims#129 (review) just triggered me to look into this some more, but I don't see how this PR changes the situation to implement what @rwjblue was talking about.

also require.moduleId now seems identical to evaluating this.id, which seems to result in the same thing!?

what would seem useful on first glance is if the _reify() method would somehow pass this.id on to the mod.module.exports() call, so that exports() knows where it was imported from and that in turn would need to provide it to the callback function in some way.

[rwjblue]

Ya, I was looking at this also. We should (in debug builds) be able to build up an array of "requirers" that we can then expose (similar to how this PR exposes require.moduleId).