Closed
Description
- Version: v16.0.0-pre
- Platform: Linux hp 4.15.0-128-generic lib: reintroduce v8 module #131-Ubuntu SMP Wed Dec 9 06:53:22 UTC 2020 i686 i686 i686 GNU/Linux
- Subsystem: build
What steps will reproduce the bug?
Build node with the --node-builtin-modules-path
option and run ./node
.
How often does it reproduce? Is there a required condition?
I had built ./node
a while back and the problem started after syncing my local copy of the repo with the main branch 3 days back.
What is the expected behavior?
No errors.
What do you see instead?
$ ./node
node:internal/bootstrap/loaders:311
if (!mod) throw new TypeError(`Missing internal module '${id}'`);
^
TypeError: Missing internal module 'internal/streams/add-abort-signal'
at nativeModuleRequire (node:internal/bootstrap/loaders:311:19)
at node:internal/streams/readable:46:5
at NativeModule.compileForInternalLoader (node:internal/bootstrap/loaders:283:7)
at nativeModuleRequire (node:internal/bootstrap/loaders:312:14)
at node:stream:40:19
at NativeModule.compileForInternalLoader (node:internal/bootstrap/loaders:283:7)
at nativeModuleRequire (node:internal/bootstrap/loaders:312:14)
at node:internal/worker/io:39:32
at NativeModule.compileForInternalLoader (node:internal/bootstrap/loaders:283:7)
at nativeModuleRequire (node:internal/bootstrap/loaders:312:14)
Additional information
To my knowledge, the generated executable is flexible enough to adapt to any js changes without another rebuild. However, ./node
seems to crash with the same error message no matter which commit I check out.