Files
node/lib/internal
Matteo Collina ba00875f01 stream: use new AsyncResource instead of bind
The bind method uses ObjectDefineProperty that shows up
in flamegraphs. This changes it to avoid the utility.

Signed-off-by: Matteo Collina <hello@matteocollina.com>
PR-URL: https://github.com/nodejs/node/pull/59867
Reviewed-By: Robert Nagy <ronagy@icloud.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Stephen Belanger <admin@stephenbelanger.com>
2025-10-07 17:29:37 +02: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-09-20 06:17:06 +00: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.