You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This implements the execArgvExtension configuration field for SEA,
which takes one of three string values to specify whether and how
execution arguments can be extended for the SEA at run time:
* `"none"`: No extension is allowed. Only the arguments specified
in `execArgv` will be used,
and the `NODE_OPTIONS` environment variable will be ignored.
* `"env"`: _(Default)_ The `NODE_OPTIONS` environment variable can
extend the execution arguments.
This is the default behavior to maintain backward compatibility.
* `"cli"`: The executable can be launched with
`--node-options="--flag1 --flag2"`, and those flags
will be parsed as execution arguments for Node.js instead of being
passed to the user script. This allows using arguments that are
not supported by the `NODE_OPTIONS` environment variable.
The `execArgvExtension` field controls how additional execution arguments can be
321
+
provided beyond those specified in the `execArgv` field. It accepts one of three string values:
322
+
323
+
* `"none"`: No extension is allowed. Only the arguments specified in `execArgv` will be used,
324
+
and the `NODE_OPTIONS` environment variable will be ignored.
325
+
* `"env"`: _(Default)_ The `NODE_OPTIONS` environment variable can extend the execution arguments.
326
+
This is the default behavior to maintain backward compatibility.
327
+
* `"cli"`: The executable can be launched with `--node-options="--flag1 --flag2"`, and those flags
328
+
will be parsed as execution arguments for Node.js instead of being passed to the user script. This allows using arguments that are not supported by the `NODE_OPTIONS`
0 commit comments