module: fix extension lookups for top-level main

The reason is that absolute URLs do not go through extension and index checks. By switching to an absolute path, the resolver still applies extensions properly to the top-level main. PR-URL: #16526 Fixes: #16476 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]>
nodejs · Oct 31, 2017 · 415fb56 · 415fb56
1 parent e683077
commit 415fb56
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 1 deletion.
diff --git a/lib/module.js b/lib/module.js
@@ -452,7 +452,7 @@ Module._load = function(request, parent, isMain) {
           ESMLoader.hook(hooks);
         }
       }
-      await ESMLoader.import(getURLFromFilePath(request).href);
+      await ESMLoader.import(getURLFromFilePath(request).pathname);
     })()
     .catch((e) => {
       console.error(e);

diff --git a/test/parallel/test-module-main-extension-lookup.js b/test/parallel/test-module-main-extension-lookup.js
@@ -0,0 +1,7 @@
+'use strict';
+require('../common');
+const { execFileSync } = require('child_process');
+
+const node = process.argv[0];
+
+execFileSync(node, ['--experimental-modules', 'test/es-module/test-esm-ok']);