Files
node/lib/internal
Philipp Dunkel 2247054dda vfs: add ZipProvider
Add a node:vfs provider backed by a node:zlib ZIP archive - a ZipBuffer
held in memory or a ZipFile on disk - that exposes the archive's members
as a virtual filesystem tree. Directories are recognized both explicitly
(a "name/" entry) and implicitly (any entry under "name/"), and a file
opened for writing commits its content as a new archive entry when its
handle is closed. The provider is read-only unless the backing archive
is writable, and offers both asynchronous and synchronous operations.
Available as vfs.ZipProvider.

Signed-off-by: Philipp Dunkel <pip@pipobscure.com>
PR-URL: https://github.com/nodejs/node/pull/64915
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
2026-09-02 07:27:11 +00:00
..
2026-07-24 14:00:18 +00:00
2026-08-01 06:15:08 +00:00
2026-08-22 07:28:28 +00:00
2026-08-15 13:15:47 -07:00
2026-08-23 03:53:29 +00:00
…
2026-09-02 07:27:11 +00:00
…
…
2026-07-24 14:00:18 +00:00
2026-08-29 00:58:18 +02:00
…
2026-07-24 14:00:18 +00:00
…
2026-08-05 13:57:32 +00:00
…
…
2026-07-24 14:00:18 +00:00
…
2026-08-23 03:31:17 +00:00
2026-05-30 09:05:23 +00:00
…
2026-08-15 13:15:47 -07: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.