Files
node/lib/internal
Ruben Bridgewater 70e7c1511f util: mark special properties when inspecting them
This makes sure special properties (such as a byteLength, buffer,
and more) are marked that they are not regular properties. They
are mostly getters, that just seemed even more of a breaking change.
Thus, they just use square brackets for now.

On top of that, it makes inspecting detached DataViews robust.
Inspecting those failed so far.

PR-URL: https://github.com/nodejs/node/pull/60131
Reviewed-By: Jordan Harband <ljharb@gmail.com>
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
2025-10-18 21:29:35 +02:00
..
2025-06-28 22:51:59 +00:00
2025-10-13 10:05:45 +02:00
2025-10-10 04:16:56 +00:00
…
…
…
…
…
2025-09-22 23:19:26 +00:00
2025-07-18 07:55:10 -07:00
2025-08-16 06:43:49 +00:00
2025-10-04 22:08:00 +02:00
…
2025-09-07 13:04:52 +00:00
2025-07-18 09:28:21 +00:00
…
2025-09-23 12:41:47 +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.