Files
node/lib/internal
Joyee Cheung 4f24aff94a module: preserve URL in the parent created by createRequire()
Previously, createRequire() does not preserve the URL it gets
passed in the mock parent module created, which can be
observable if it's used together with module.registerHooks().
This patch adds preservation of the URL if createRequire()
is invoked with one.

PR-URL: https://github.com/nodejs/node/pull/60974
Fixes: https://github.com/nodejs/node/issues/60973
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com>
2025-12-13 07:36:20 +00:00
..
2025-10-13 10:05:45 +02:00
2025-11-30 19:14:12 +01:00
2025-12-12 12:34:21 +00:00
2025-12-10 16:12:28 +00:00
2025-08-16 06:43:49 +00:00
2025-10-04 22:08:00 +02:00
2025-12-12 12:34:21 +00:00
2025-11-23 17:13:58 +00:00

Internal Modules

The modules located in lib/internal directory are exclusively meant for internal usage within the Node.js core. They are not intended to be accessed via user modules require(). These modules may change at any point in time. Relying on these internal modules outside the core is not supported and can lead to unpredictable behavior.

In certain scenarios, accessing these internal modules for debugging or experimental purposes might be necessary. Node.js provides the --expose-internals flag to expose these modules to userland code. This flag only exists to assist Node.js maintainers with debugging internals. It is not meant for use outside the project.