Version
^22.4.0
main with the --no-experimental-require-module flag.
Platform
Subsystem
esm,module
What steps will reproduce the bug?
mkdir undefined && cd undefined
echo '{"type":"module"}' > package.json
echo "import nothing from 'somewhere'" > app.js
echo "require('./app.js')" > test.cjs
node test.cjs
How often does it reproduce? Is there a required condition?
It starts to happen with v22.4.0. v20.x and <=22.3.0 are not affected.
What is the expected behavior? Why is that the expected behavior?
$ node test.cjs
/Users/mzasso/git/test/undefined/test.cjs:1
require('./app.js')
^
Error [ERR_REQUIRE_ESM]: require() of ES Module /Users/mzasso/git/test/undefined/app.js from /Users/mzasso/git/test/undefined/test.cjs not supported.
Instead change the require of app.js in /Users/mzasso/git/test/undefined/test.cjs to a dynamic import() which is available in all CommonJS modules.
at Object.<anonymous> (/Users/mzasso/git/test/undefined/test.cjs:1:1) {
code: 'ERR_REQUIRE_ESM'
}
Node.js v22.3.0
What do you see instead?
$ node test.cjs
/Users/mzasso/git/test/undefined/test.cjs:315
undefined
^
Error [ERR_REQUIRE_ESM]: require() of ES Module /Users/mzasso/git/test/undefined/app.js from /Users/mzasso/git/test/undefined/test.cjs not supported.
Instead change the require of app.js in /Users/mzasso/git/test/undefined/test.cjs to a dynamic import() which is available in all CommonJS modules.
at TracingChannel.traceSync (node:diagnostics_channel:315:14)
at Object.<anonymous> (/Users/mzasso/git/test/undefined/test.cjs:1:1) {
code: 'ERR_REQUIRE_ESM'
}
Node.js v22.4.0
Additional information
As you can see, this seems to be caused by the presence of TracingChannel.traceSync in the stack trace.
Version
^22.4.0mainwith the--no-experimental-require-moduleflag.Platform
Subsystem
esm,module
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
It starts to happen with v22.4.0. v20.x and <=22.3.0 are not affected.
What is the expected behavior? Why is that the expected behavior?
What do you see instead?
Additional information
As you can see, this seems to be caused by the presence of
TracingChannel.traceSyncin the stack trace.