Files
node/lib/internal
Chengzhong Wu 787e93f75a inspector: add Network.Initiator in inspector protocol
Add initiator stack trace in inspector network events, reflecting
the location where the script created the request.

The `http.client.request.created` event is closer to where user code
creates the http request, and correctly reflects which script
initiated the request.

PR-URL: https://github.com/nodejs/node/pull/56805
Refs: https://github.com/nodejs/node/issues/53946
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Kohei Ueno <kohei.ueno119@gmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
2025-04-16 03:29:17 -03:00
..
2024-11-27 11:03:39 -05:00
2024-10-04 10:20:24 +02:00
2024-10-04 10:20:26 +02:00
2025-02-06 01:15:06 +01:00
2024-11-27 11:03:39 -05:00
2024-09-12 11:06:49 +02:00
2024-04-29 22:46:31 +02:00
2024-11-27 11:03:39 -05:00
2024-11-27 11:03:39 -05:00
2025-04-16 03:29:16 -03:00
…
…
2024-10-04 10:20:24 +02:00
…
2025-01-05 12:57:35 -05:00
2024-10-04 10:20:24 +02:00
2024-08-30 15:52:14 -03:00
2024-02-19 01:19:44 +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.