vfs: unflag

Signed-off-by: Matteo Collina <hello@matteocollina.com>

Author: mcollina

doc/api/cli.md

@@ -285,7 +285,7 @@ so mounting one is gated on its own flag rather than on `--allow-fs-read` or
 `--allow-fs-write`.
 
 ```console
-$ node --experimental-vfs --permission --allow-fs-vfs app.js
+$ node --permission --allow-fs-vfs app.js
 ```
 
 ### `--allow-fs-write`
@@ -1671,16 +1671,6 @@ with AND, so a test must satisfy every expression to run.
 A malformed expression causes the test runner to exit with a non-zero status
 before running any tests.
 
-### `--experimental-vfs`
-
-<!-- YAML
-added: v26.4.0
--->
-
-> Stability: 1 - Experimental
-
-Enable the experimental [`node:vfs`][] module.
-
 ### `--experimental-vm-modules`
 
 <!-- YAML
@@ -3859,7 +3849,7 @@ added: v26.10.0
 
 * `source` {string} A directory or an archive file to mount and run.
 
-Requires [`--experimental-vfs`][]. May be given at most once.
+May be given at most once.
 
 Mounts `source` as a virtual file system ([`node:vfs`][]), and runs the entry
 point and all subsequent `require()`/`import` resolution against that mount
@@ -3894,18 +3884,17 @@ same thing in all of them.
 
 A worker created with its own `execArgv` inherits none of the parent's options,
 and so does not mount the source at all. To run a script from the mount, such a
-worker must be given the same options again, `--experimental-vfs` and
-`--vfs-load`; without them, that thread has no mount for the script to come
-from, and the worker fails to load it. `--experimental-vfs` is also what makes
-[`node:vfs`][] available to the worker's own code. A worker whose script comes
-from anywhere else, such as the real file system, needs nothing added.
+worker must be given `--vfs-load` again; without it, that thread has no mount
+for the script to come from, and the worker fails to load it. [`node:vfs`][] is
+available to worker code without an experimental flag. A worker whose script
+comes from anywhere else, such as the real file system, needs nothing added.
 
 `--vfs-load` is not permitted in [`NODE_OPTIONS`][]: which entry point runs is
 the command line's decision, and the environment must not be able to redirect
 it.
 
 ```console
-$ node --experimental-vfs --vfs-load=app.zip
+$ node --vfs-load=app.zip
 ```
 
 ### `--watch`
@@ -4231,7 +4220,6 @@ one is included in the list below.
 * `--experimental-stream-iter`
 * `--experimental-test-isolation`
 * `--experimental-top-level-await`
-* `--experimental-vfs`
 * `--experimental-vm-modules`
 * `--experimental-wasi-unstable-preview1`
 * `--experimental-web-worker`
@@ -4864,7 +4852,6 @@ node --stack-trace-limit=12 -p -e "Error.stackTraceLimit" # prints 12
 [`--env-file-if-exists`]: #--env-file-if-existsfile
 [`--env-file`]: #--env-filefile
 [`--experimental-sea-config`]: single-executable-applications.md#1-generating-single-executable-preparation-blobs
-[`--experimental-vfs`]: #--experimental-vfs
 [`--heap-prof-dir`]: #--heap-prof-dir
 [`--import`]: #--importmodule
 [`--no-require-module`]: #--no-require-module

doc/api/vfs.md

@@ -24,8 +24,8 @@ import vfs from 'node:vfs';
 const vfs = require('node:vfs');
 ```
 
-This module is only available under the `node:` scheme, and only when Node.js
-is started with the `--experimental-vfs` flag.
+This module is only available under the `node:` scheme. Loading it emits an
+`ExperimentalWarning`.
 
 ## Security
 
@@ -77,8 +77,9 @@ added: v26.4.0
 * `provider` {VirtualProvider} The provider to use. **Default:**
   `new MemoryProvider()`.
 * `options` {Object}
-  * `emitExperimentalWarning` {boolean} Whether to emit the experimental
-    warning when the instance is created. **Default:** `true`.
+  * `emitExperimentalWarning` {boolean} Whether to emit an experimental warning
+    when an instance is created. **Default:** `true`. Loading `node:vfs` emits
+    the warning regardless of this option.
 * Returns: {VirtualFileSystem}
 
 Convenience factory equivalent to `new VirtualFileSystem(provider, options)`.
@@ -148,7 +149,7 @@ vfs.registerProvider({
 ```
 
 ```console
-$ node --experimental-vfs --require ./provider.js \
+$ node --require ./provider.js \
        --vfs-load archive.customfmt
 ```
 
@@ -193,8 +194,9 @@ added: v26.4.0
 * `provider` {VirtualProvider} The provider to use. **Default:**
   `new MemoryProvider()`.
 * `options` {Object}
-  * `emitExperimentalWarning` {boolean} Whether to emit the experimental
-    warning. **Default:** `true`.
+  * `emitExperimentalWarning` {boolean} Whether to emit an experimental warning
+    when an instance is created. **Default:** `true`. Loading `node:vfs` emits
+    the warning regardless of this option.
 
 ### `vfs.mount()`
 

doc/node.1

@@ -174,7 +174,7 @@ A mounted VFS serves paths that the file system permissions do not describe,
 so mounting one is gated on its own flag rather than on \fB--allow-fs-read\fR or
 \fB--allow-fs-write\fR.
 .Bd -literal
-$ node --experimental-vfs --permission --allow-fs-vfs app.js
+$ node --permission --allow-fs-vfs app.js
 .Ed
 .
 .It Fl -allow-fs-write
@@ -896,9 +896,6 @@ with AND, so a test must satisfy every expression to run.
 A malformed expression causes the test runner to exit with a non-zero status
 before running any tests.
 .
-.It Fl -experimental-vfs
-Enable the experimental \fBnode:vfs\fR module.
-.
 .It Fl -experimental-vm-modules
 Enable experimental ES Module support in the \fBnode:vm\fR module.
 .
@@ -1932,7 +1929,7 @@ Print node's version.
 .It
 \fBsource\fR \fB{string}\fR A directory or an archive file to mount and run.
 .El
-Requires \fB--experimental-vfs\fR. May be given at most once.
+May be given at most once.
 Mounts \fBsource\fR as a virtual file system (\fBnode:vfs\fR), and runs the entry
 point and all subsequent \fBrequire()\fR/\fBimport\fR resolution against that mount
 rather than the real file system. The mount is placed at a reserved mount point
@@ -1963,16 +1960,15 @@ mounts it, whatever else that thread mounts, so a path into the mount means the
 same thing in all of them.
 A worker created with its own \fBexecArgv\fR inherits none of the parent's options,
 and so does not mount the source at all. To run a script from the mount, such a
-worker must be given the same options again, \fB--experimental-vfs\fR and
-\fB--vfs-load\fR; without them, that thread has no mount for the script to come
-from, and the worker fails to load it. \fB--experimental-vfs\fR is also what makes
-\fBnode:vfs\fR available to the worker's own code. A worker whose script comes
-from anywhere else, such as the real file system, needs nothing added.
+worker must be given \fB--vfs-load\fR again; without it, that thread has no mount
+for the script to come from, and the worker fails to load it. \fBnode:vfs\fR is
+available to worker code without an experimental flag. A worker whose script
+comes from anywhere else, such as the real file system, needs nothing added.
 \fB--vfs-load\fR is not permitted in \fBNODE_OPTIONS\fR: which entry point runs is
 the command line's decision, and the environment must not be able to redirect
 it.
 .Bd -literal
-$ node --experimental-vfs --vfs-load=app.zip
+$ node --vfs-load=app.zip
 .Ed
 .
 .It Fl -watch
@@ -2228,8 +2224,6 @@ one is included in the list below.
 .It
 \fB--experimental-top-level-await\fR
 .It
-\fB--experimental-vfs\fR
-.It
 \fB--experimental-vm-modules\fR
 .It
 \fB--experimental-wasi-unstable-preview1\fR

lib/internal/process/pre_execution.js

@@ -524,10 +524,6 @@ function setupQuic() {
 }
 
 function setupVfs() {
-  if (!getOptionValue('--experimental-vfs')) {
-    return;
-  }
-
   const { BuiltinModule } = require('internal/bootstrap/realm');
   BuiltinModule.allowRequireByUsers('vfs');
 }

lib/internal/vfs/file_system.js

@@ -15,7 +15,6 @@ const {
     ERR_INVALID_STATE,
   },
 } = require('internal/errors');
-const { validateBoolean } = require('internal/validators');
 const { MemoryProvider } = require('internal/vfs/providers/memory');
 const path = require('path');
 const { posix: pathPosix, resolve: resolvePath, sep, toNamespacedPath } = path;
@@ -39,6 +38,7 @@ const {
 const { VirtualReadStream, VirtualWriteStream } = require('internal/vfs/streams');
 const { VirtualDir } = require('internal/vfs/dir');
 const { emitExperimentalWarning, kEmptyObject } = require('internal/util');
+const { validateBoolean } = require('internal/validators');
 let debug = require('internal/util/debuglog').debuglog('vfs', (fn) => {
   debug = fn;
 });
@@ -111,7 +111,6 @@ class VirtualFileSystem {
   /**
    * @param {VirtualProvider|object} [providerOrOptions] The provider to use, or options
    * @param {object} [options] Configuration options
-   * @param {boolean} [options.emitExperimentalWarning] Emit the experimental warning (default: true)
    */
   constructor(providerOrOptions, options = kEmptyObject) {
     let provider = null;

lib/vfs.js

@@ -4,6 +4,9 @@ const {
   FunctionPrototypeSymbolHasInstance,
 } = primordials;
 
+const { emitExperimentalWarning } = require('internal/util');
+emitExperimentalWarning('VirtualFileSystem');
+
 const { VirtualFileSystem } = require('internal/vfs/file_system');
 const { VirtualProvider } = require('internal/vfs/provider');
 const { MemoryProvider } = require('internal/vfs/providers/memory');

src/node.cc

@@ -1049,9 +1049,6 @@ static ExitCode InitializeNodeWithArgsInternal(
   // count below needs the arguments the command line itself gave.
   {
     auto* env_options = per_process::cli_options->per_isolate->per_env.get();
-    if (!env_options->experimental_vfs && env_options->vfs_load) {
-      errors->push_back("--vfs-load requires --experimental-vfs");
-    }
     // A second --vfs-load would silently replace the first, and the option
     // itself cannot say how often it was given; count it in the node options
     // the command line yielded.

src/node_options.cc

@@ -789,8 +789,9 @@ EnvironmentOptionsParser::EnvironmentOptionsParser() {
             NoOp{},
 #endif
             kAllowedInEnvvar);
+  // Retained as a no-op for compatibility; node:vfs is no longer gated.
   AddOption("--experimental-vfs",
-            "experimental node:vfs module",
+            "",
             BOOL_FIELD(experimental_vfs),
             kAllowedInEnvvar);
   // Choosing the entry point is the command line's alone: an environment
@@ -801,7 +802,7 @@ EnvironmentOptionsParser::EnvironmentOptionsParser() {
   AddOption("--vfs-load",
             "mount a directory or archive as a virtual file system and run the "
             "entry point and module resolution against it instead of the real "
-            "file system (may be given once; requires --experimental-vfs)",
+            "file system (may be given once)",
             &EnvironmentOptions::vfs_load_source,
             kDisallowedInEnvvar);
   AddOption("[vfs_load_set]", "", BOOL_FIELD(vfs_load));

test/ffi/test-ffi-vfs.js

@@ -1,4 +1,4 @@
-// Flags: --experimental-vfs
+// Flags: --disable-warning=ExperimentalWarning
 'use strict';
 const common = require('../common');
 common.skipIfFFIMissing();

test/parallel/test-module-builtin-experimental.js

@@ -1,3 +1,4 @@
+// Flags: --disable-warning=ExperimentalWarning
 'use strict';
 
 const common = require('../common');
@@ -8,7 +9,6 @@ const experimentalBuiltins = [
   ['bench/reporters', '--experimental-bench', true],
   ['dtls', '--experimental-dtls', common.hasDtls],
   ['quic', '--experimental-quic', common.hasQuic],
-  ['vfs', '--experimental-vfs', true],
 ].filter(([, , available]) => available);
 
 for (const [id, flag] of experimentalBuiltins) {
@@ -51,7 +51,7 @@ if (common.hasFFI) {
   ], { status: 0 });
 }
 
-const schemeOnlyBuiltins = ['node:test', 'node:sea'];
+const schemeOnlyBuiltins = ['node:test', 'node:sea', 'node:vfs'];
 if (common.hasFFI) {
   schemeOnlyBuiltins.push('node:ffi');
 }