esm: irp type implementation
Refs: https://github.com/GeoffreyBooth/node-import-file-specifier-resolution-proposal Refs: nodejs/modules#180 Refs: nodejs/ecmascript-modules#6 Refs: nodejs/ecmascript-modules#12 Refs: nodejs/ecmascript-modules#28 Co-authored-by: Myles Borins <MylesBorins@google.com> Co-authored-by: John-David Dalton <john.david.dalton@gmail.com>

Refs: https://github.com/GeoffreyBooth/node-import-file-specifier-resolution-proposal Refs: nodejs/modules#180 Refs: nodejs/ecmascript-modules#6 Refs: nodejs/ecmascript-modules#12 Refs: nodejs/ecmascript-modules#28 Co-authored-by: Myles Borins <MylesBorins@google.com> Co-authored-by: John-David Dalton <john.david.dalton@gmail.com>
esm: add experimental .json support to loader
With the new flag `--experimental-json-modules` it is now possible to import .json files. It piggy backs on the current cjs loader implementation, so it only exports a default. This is a bit of a hack, and it should potentially have it's own loader, especially if we change the cjs loader at all. The behavior for .json in the cjs loader matches the current planned behavior if json modules were to be standardized, specifically that a .json module only exports a default. Refs: nodejs/modules#255 Refs: whatwg/html#4315 Refs: w3c/webcomponents#770
nodejs · MylesBorins · MylesBorins · MylesBorins · Mar 18, 2019 · nodejs-github-bot
diff --git a/lib/internal/errors.js b/lib/internal/errors.js
+    return `Cannot use ${typeString} because nearest parent package.json ` +
+      ((typeFlag === 'module') ?
+        'includes "type": "commonjs"' : 'includes "type": "module",') +
+      ` which controls the type to use for ${filename}`;
diff --git a/doc/api/esm.md b/doc/api/esm.md
diff --git a/doc/api/cli.md b/doc/api/cli.md
diff --git a/doc/api/cli.md b/doc/api/cli.md
diff --git a/doc/api/esm.md b/doc/api/esm.md
diff --git a/lib/internal/errors.js b/lib/internal/errors.js
diff --git a/doc/api/cli.md b/doc/api/cli.md
diff --git a/doc/api/esm.md b/doc/api/esm.md
diff --git a/doc/api/esm.md b/doc/api/esm.md
diff --git a/doc/api/cli.md b/doc/api/cli.md
+added: REPLACEME
+-->
+
+To be used in conjunction with `--experimental modules`. Sets the resolution
diff --git a/lib/internal/errors.js b/lib/internal/errors.js
+  else if (conflict === 'scope')
+    return `Cannot use ${typeString} because nearest parent package.json ` +
+      ((typeFlag === 'module') ?
+        'includes "type": "commonjs"' : 'includes "type": "module",') +
diff --git a/test/message/esm_display_syntax_error.out b/test/message/esm_display_syntax_error.out
 SyntaxError: Unexpected reserved word
-    at internal/modules/esm/translators.js:*:*
+    at Loader.<anonymous> (internal/modules/esm/translators.js:*:*)
diff --git a/test/es-module/test-esm-no-extension.js b/test/es-module/test-esm-no-extension.js
+
+const entry = fixtures.path('/es-modules/noext-esm');
+
+const child = spawn(process.execPath, [
diff --git a/src/node_options.cc b/src/node_options.cc
@@ -301,6 +333,10 @@ EnvironmentOptionsParser::EnvironmentOptionsParser() {
            "show stack traces on process warnings",
            &EnvironmentOptions::trace_warnings,
            kAllowedInEnvironment);
+  AddOption("--entry-type",
+            "top-level module type name",
diff --git a/src/module_wrap.h b/src/module_wrap.h
@@ -29,11 +24,6 @@ enum HostDefinedOptions : int {
  kLength = 10,
 };

-v8::Maybe<url::URL> Resolve(Environment* env,
diff --git a/lib/internal/process/execution.js b/lib/internal/process/execution.js
+    process.exit(1);
+  });
+  // Handle any nextTicks added in the first tick of the program.
+  process._tickCallback();
diff --git a/lib/internal/modules/esm/module_job.js b/lib/internal/modules/esm/module_job.js
@@ -101,8 +101,7 @@ class ModuleJob {

  async run() {
    const module = await this.instantiate();
-    module.evaluate(-1, false);
-    return module;
+    return { module, result: module.evaluate(-1, false) };