Closure-compiler: buildRegistry in ModuleLoader doesn't handle case of immediate node_modules

[cramforce]

E.g. if an input is node_modules/left-pad/index.js that never hits the split for /node_modules/ and thus isn't subject to the resolve algorithm.

CC @ChadKillingsworth

[ChadKillingsworth]

Thanks. I hadn't seen this case because the grunt and gulp plugins don't use file paths like that.

[ChadKillingsworth]

The fix for this is part of #2130

[cramforce]

Nice, also fixes my next feature request :)

On Tue, Nov 29, 2016 at 11:02 AM, Chad Killingsworth <
[email protected]> wrote:

The fix for this is part of #2130
https://github.com/google/closure-compiler/pull/2130

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/closure-compiler/issues/2170#issuecomment-263665201,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFeT6k9VR6Y8poCl20TPv_kpbwZf8FQks5rDHbUgaJpZM4K7U4K
.

[ChadKillingsworth]

That PR is the culmination of a year's work.

[ChadKillingsworth]

Closed by #2130