Files
node/lib/internal
Joyee Cheung d55c3e7f0b esm: link modules synchronously when no async loader hooks are used
When no async loader hooks are registered, perform the linking as
synchronously as possible to reduce the chance of races from the
the shared module loading cache.

PR-URL: https://github.com/nodejs/node/pull/59519
Fixes: https://github.com/nodejs/node/issues/59366
Refs: https://github.com/abejfehr/node-22.18-issue-repro
Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
2025-09-20 04:32:39 +00:00
..
2025-08-25 17:02:49 +02:00
2024-11-27 11:03:39 -05:00
2025-08-04 12:25:31 +02:00
2025-07-28 08:46:16 +02:00
2025-08-26 11:22:42 +02:00
…
2024-09-12 11:06:49 +02:00
2024-11-27 11:03:39 -05:00
2025-07-24 20:08:23 +02:00
…
…
2025-04-17 10:51:13 -03:00
…
2025-01-05 12:57:35 -05:00
2025-07-24 20:08:23 +02:00
…
2025-09-20 03:32:52 +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.