module: do not warn when require(esm) comes from node_modules

As part of the standard experimental feature graduation policy, when we unflagged require(esm) we moved the experimental warning to be emitted when require() is actually used to load ESM, which previously was an error. However, some packages in the ecosystem have already being using try-catch to load require(esm) to e.g. resolve optional dependency, and emitting warning from there instead of throwing directly could break the CLI output. To reduce the disruption for releases, as a compromise, this patch skips the warning if require(esm) comes from node_modules, where users typically don't have much control over the code. This warning will be eventually removed when require(esm) becomes stable. This patch was originally intended for the LTS releases, though it seems there's appetite for it on v23.x as well so it's re-targeted to the main branch. PR-URL: #55960 Backport-PR-URL: #56927 Refs: #55217 Refs: #52697 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Jacob Smith <jacob@frende.me>

Author: joyeecheung

lib/internal/modules/cjs/loader.js

@@ -70,6 +70,7 @@ const {
  module_export_private_symbol,
  module_parent_private_symbol,
  },
+ isInsideNodeModules,
 } = internalBinding('util');
 
 const { kEvaluated, createRequiredModuleFacade } = internalBinding('module_wrap');
@@ -126,6 +127,7 @@ const {
  kEmptyObject,
  setOwnProperty,
  getLazy,
+ isUnderNodeModules,
 } = require('internal/util');
 const {
  makeContextifyScript,
@@ -1314,6 +1316,7 @@ Module.prototype.require = function(id) {
  }
 };
 
+let emittedRequireModuleWarning = false;
 /**
  * Resolved path to `process.argv[1]` will be lazily placed here
  * (needed for setting breakpoint when called with `--inspect-brk`).
@@ -1341,29 +1344,46 @@ function loadESMFromCJS(mod, filename) {
  setOwnProperty(process, 'mainModule', undefined);
  } else {
  const parent = mod[kModuleParent];
- let messagePrefix;
- if (parent) {
- // In the case of the module calling `require()`, it's more useful to know its absolute path.
- let from = parent.filename || parent.id;
- // In the case of the module being require()d, it's more useful to know the id passed into require().
- const to = mod.id || mod.filename;
- if (from === 'internal/preload') {
- from = '--require';
- } else if (from === '<repl>') {
- from = 'The REPL';
- } else if (from === '.') {
- from = 'The entry point';
- } else {
- from &&= `CommonJS module ${from}`;
+
+ if (!emittedRequireModuleWarning) {
+ let shouldEmitWarning = false;
+ // Check if the require() comes from node_modules.
+ if (parent) {
+ shouldEmitWarning = !isUnderNodeModules(parent.filename);
+ } else if (mod[kIsCachedByESMLoader]) {
+ // It comes from the require() built for `import cjs` and doesn't have a parent recorded
+ // in the CJS module instance. Inspect the stack trace to see if the require()
+ // comes from node_modules and reduce the noise. If there are more than 100 frames,
+ // just give up and assume it is under node_modules.
+ shouldEmitWarning = !isInsideNodeModules(100, true);
  }
- if (from && to) {
- messagePrefix = `${from} is loading ES Module ${to} using require().\n`;
+ if (shouldEmitWarning) {
+ let messagePrefix;
+ if (parent) {
+ // In the case of the module calling `require()`, it's more useful to know its absolute path.
+ let from = parent.filename || parent.id;
+ // In the case of the module being require()d, it's more useful to know the id passed into require().
+ const to = mod.id || mod.filename;
+ if (from === 'internal/preload') {
+ from = '--require';
+ } else if (from === '<repl>') {
+ from = 'The REPL';
+ } else if (from === '.') {
+ from = 'The entry point';
+ } else {
+ from &&= `CommonJS module ${from}`;
+ }
+ if (from && to) {
+ messagePrefix = `${from} is loading ES Module ${to} using require().\n`;
+ }
+ }
+ emitExperimentalWarning('Support for loading ES Module in require()',
+ messagePrefix,
+ undefined,
+ parent?.require);
+ emittedRequireModuleWarning = true;
  }
  }
- emitExperimentalWarning('Support for loading ES Module in require()',
- messagePrefix,
- undefined,
- parent?.require);
  const {
  wrap,
  namespace,

test/es-module/test-require-node-modules-warning.js

@@ -0,0 +1,59 @@
+'use strict';
+
+// This checks the experimental warning for require(esm) is disabled when the
+// require() comes from node_modules.
+require('../common');
+const { spawnSyncAndAssert } = require('../common/child_process');
+const fixtures = require('../common/fixtures');
+
+const warningRE = /Support for loading ES Module in require\(\)/;
+
+// The fixtures are placed in a directory that includes "node_modules" in its name
+// to check false negatives.
+
+// require() in non-node_modules -> esm in node_modules should warn.
+spawnSyncAndAssert(
+ process.execPath,
+ [fixtures.path('es-modules', 'test_node_modules', 'require-esm.js')],
+ {
+ trim: true,
+ stderr: warningRE,
+ stdout: 'world',
+ }
+);
+
+// require() in non-node_modules -> require() in node_modules -> esm in node_modules
+// should not warn.
+spawnSyncAndAssert(
+ process.execPath,
+ [fixtures.path('es-modules', 'test_node_modules', 'require-require-esm.js')],
+ {
+ trim: true,
+ stderr: '',
+ stdout: 'world',
+ }
+);
+
+// Import in non-node_modules -> require() in node_modules -> esm in node_modules
+// should not warn.
+spawnSyncAndAssert(
+ process.execPath,
+ [fixtures.path('es-modules', 'test_node_modules', 'import-require-esm.mjs')],
+ {
+ trim: true,
+ stderr: '',
+ stdout: 'world',
+ }
+);
+
+// Import in non-node_modules -> import in node_modules ->
+// require() in node_modules -> esm in node_modules should not warn.
+spawnSyncAndAssert(
+ process.execPath,
+ [fixtures.path('es-modules', 'test_node_modules', 'import-import-require-esm.mjs')],
+ {
+ trim: true,
+ stderr: '',
+ stdout: 'world',
+ }
+);