dsh-x-core 0.1.23 → 0.1.25

package/node/node_modules/npm/man/man1/npm.1

@@ -1,131 +1,131 @@
-.TH "NPM" "1" "June 2025" "NPM@10.9.3" ""
-.SH "NAME"
-\fBnpm\fR - javascript package manager
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npm
-.fi
-.RE
-.P
-Note: This command is unaware of workspaces.
-.SS "Version"
-.P
-10.9.3
-.SS "Description"
-.P
-npm is the package manager for the Node JavaScript platform. It puts modules in place so that node can find them, and manages dependency conflicts intelligently.
-.P
-It is extremely configurable to support a variety of use cases. Most commonly, you use it to publish, discover, install, and develop node programs.
-.P
-Run \fBnpm help\fR to get a list of available commands.
-.SS "Important"
-.P
-npm comes preconfigured to use npm's public registry at https://registry.npmjs.org by default. Use of the npm public registry is subject to terms of use available at https://docs.npmjs.com/policies/terms.
-.P
-You can configure npm to use any compatible registry you like, and even run your own registry. Use of someone else's registry is governed by their terms of use.
-.SS "Introduction"
-.P
-You probably got npm because you want to install stuff.
-.P
-The very first thing you will most likely want to run in any node program is \fBnpm install\fR to install its dependencies.
-.P
-You can also run \fBnpm install blerg\fR to install the latest version of "blerg". Check out npm help install for more info. It can do a lot of stuff.
-.P
-Use the \fBnpm search\fR command to show everything that's available in the public registry. Use \fBnpm ls\fR to show everything you've installed.
-.SS "Dependencies"
-.P
-If a package lists a dependency using a git URL, npm will install that dependency using the \fB\fBgit\fR\fR \fI\(lahttps://github.com/git-guides/install-git\(ra\fR command and will generate an error if it is not installed.
-.P
-If one of the packages npm tries to install is a native node module and requires compiling of C++ Code, npm will use \fBnode-gyp\fR \fI\(lahttps://github.com/nodejs/node-gyp\(ra\fR for that task. For a Unix system, \fBnode-gyp\fR \fI\(lahttps://github.com/nodejs/node-gyp\(ra\fR needs Python, make and a buildchain like GCC. On Windows, Python and Microsoft Visual Studio C++ are needed. For more information visit \fBthe node-gyp repository\fR \fI\(lahttps://github.com/nodejs/node-gyp\(ra\fR and the \fBnode-gyp Wiki\fR \fI\(lahttps://github.com/nodejs/node-gyp/wiki\(ra\fR.
-.SS "Directories"
-.P
-See npm help folders to learn about where npm puts stuff.
-.P
-In particular, npm has two modes of operation:
-.RS 0
-.IP \(bu 4
-local mode: npm installs packages into the current project directory, which defaults to the current working directory. Packages install to \fB./node_modules\fR, and bins to \fB./node_modules/.bin\fR.
-.IP \(bu 4
-global mode: npm installs packages into the install prefix at \fB$npm_config_prefix/lib/node_modules\fR and bins to \fB$npm_config_prefix/bin\fR.
-.RE 0
-
-.P
-Local mode is the default. Use \fB-g\fR or \fB--global\fR on any command to run in global mode instead.
-.SS "Developer Usage"
-.P
-If you're using npm to develop and publish your code, check out the following help topics:
-.RS 0
-.IP \(bu 4
-json: Make a package.json file. See \fB\fBpackage.json\fR\fR \fI\(la/configuring-npm/package-json\(ra\fR.
-.IP \(bu 4
-link: Links your current working code into Node's path, so that you don't have to reinstall every time you make a change. Use npm help link to do this.
-.IP \(bu 4
-install: It's a good idea to install things if you don't need the symbolic link. Especially, installing other peoples code from the registry is done via npm help install
-.IP \(bu 4
-adduser: Create an account or log in. When you do this, npm will store credentials in the user config file.
-.IP \(bu 4
-publish: Use the npm help publish command to upload your code to the registry.
-.RE 0
-
-.SS "Configuration"
-.P
-npm is extremely configurable. It reads its configuration options from 5 places.
-.RS 0
-.IP \(bu 4
-Command line switches: Set a config with \fB--key val\fR. All keys take a value, even if they are booleans (the config parser doesn't know what the options are at the time of parsing). If you do not provide a value (\fB--key\fR) then the option is set to boolean \fBtrue\fR.
-.IP \(bu 4
-Environment Variables: Set any config by prefixing the name in an environment variable with \fBnpm_config_\fR. For example, \fBexport npm_config_key=val\fR.
-.IP \(bu 4
-User Configs: The file at \fB$HOME/.npmrc\fR is an ini-formatted list of configs. If present, it is parsed. If the \fBuserconfig\fR option is set in the cli or env, that file will be used instead.
-.IP \(bu 4
-Global Configs: The file found at \fB./etc/npmrc\fR (relative to the global prefix will be parsed if it is found. See npm help prefix for more info on the global prefix. If the \fBglobalconfig\fR option is set in the cli, env, or user config, then that file is parsed instead.
-.IP \(bu 4
-Defaults: npm's default configuration options are defined in \fBlib/utils/config/definitions.js\fR. These must not be changed.
-.RE 0
-
-.P
-See npm help config for much much more information.
-.SS "Contributions"
-.P
-Patches welcome!
-.P
-If you would like to help, but don't know what to work on, read the \fBcontributing guidelines\fR \fI\(lahttps://github.com/npm/cli/blob/latest/CONTRIBUTING.md\(ra\fR and check the issues list.
-.SS "Bugs"
-.P
-When you find issues, please report them: \fI\(lahttps://github.com/npm/cli/issues\(ra\fR
-.P
-Please be sure to follow the template and bug reporting guidelines.
-.SS "Feature Requests"
-.P
-Discuss new feature ideas on our discussion forum:
-.RS 0
-.IP \(bu 4
-\fI\(lahttps://github.com/orgs/community/discussions/categories/npm\(ra\fR
-.RE 0
-
-.P
-Or suggest formal RFC proposals:
-.RS 0
-.IP \(bu 4
-\fI\(lahttps://github.com/npm/rfcs\(ra\fR
-.RE 0
-
-.SS "See Also"
-.RS 0
-.IP \(bu 4
-npm help help
-.IP \(bu 4
-\fBpackage.json\fR \fI\(la/configuring-npm/package-json\(ra\fR
-.IP \(bu 4
-npm help npmrc
-.IP \(bu 4
-npm help config
-.IP \(bu 4
-npm help install
-.IP \(bu 4
-npm help prefix
-.IP \(bu 4
-npm help publish
-.RE 0
+.TH "NPM" "1" "June 2025" "NPM@10.9.3" ""
+.SH "NAME"
+\fBnpm\fR - javascript package manager
+.SS "Synopsis"
+.P
+.RS 2
+.nf
+npm
+.fi
+.RE
+.P
+Note: This command is unaware of workspaces.
+.SS "Version"
+.P
+10.9.3
+.SS "Description"
+.P
+npm is the package manager for the Node JavaScript platform. It puts modules in place so that node can find them, and manages dependency conflicts intelligently.
+.P
+It is extremely configurable to support a variety of use cases. Most commonly, you use it to publish, discover, install, and develop node programs.
+.P
+Run \fBnpm help\fR to get a list of available commands.
+.SS "Important"
+.P
+npm comes preconfigured to use npm's public registry at https://registry.npmjs.org by default. Use of the npm public registry is subject to terms of use available at https://docs.npmjs.com/policies/terms.
+.P
+You can configure npm to use any compatible registry you like, and even run your own registry. Use of someone else's registry is governed by their terms of use.
+.SS "Introduction"
+.P
+You probably got npm because you want to install stuff.
+.P
+The very first thing you will most likely want to run in any node program is \fBnpm install\fR to install its dependencies.
+.P
+You can also run \fBnpm install blerg\fR to install the latest version of "blerg". Check out npm help install for more info. It can do a lot of stuff.
+.P
+Use the \fBnpm search\fR command to show everything that's available in the public registry. Use \fBnpm ls\fR to show everything you've installed.
+.SS "Dependencies"
+.P
+If a package lists a dependency using a git URL, npm will install that dependency using the \fB\fBgit\fR\fR \fI\(lahttps://github.com/git-guides/install-git\(ra\fR command and will generate an error if it is not installed.
+.P
+If one of the packages npm tries to install is a native node module and requires compiling of C++ Code, npm will use \fBnode-gyp\fR \fI\(lahttps://github.com/nodejs/node-gyp\(ra\fR for that task. For a Unix system, \fBnode-gyp\fR \fI\(lahttps://github.com/nodejs/node-gyp\(ra\fR needs Python, make and a buildchain like GCC. On Windows, Python and Microsoft Visual Studio C++ are needed. For more information visit \fBthe node-gyp repository\fR \fI\(lahttps://github.com/nodejs/node-gyp\(ra\fR and the \fBnode-gyp Wiki\fR \fI\(lahttps://github.com/nodejs/node-gyp/wiki\(ra\fR.
+.SS "Directories"
+.P
+See npm help folders to learn about where npm puts stuff.
+.P
+In particular, npm has two modes of operation:
+.RS 0
+.IP \(bu 4
+local mode: npm installs packages into the current project directory, which defaults to the current working directory. Packages install to \fB./node_modules\fR, and bins to \fB./node_modules/.bin\fR.
+.IP \(bu 4
+global mode: npm installs packages into the install prefix at \fB$npm_config_prefix/lib/node_modules\fR and bins to \fB$npm_config_prefix/bin\fR.
+.RE 0
+
+.P
+Local mode is the default. Use \fB-g\fR or \fB--global\fR on any command to run in global mode instead.
+.SS "Developer Usage"
+.P
+If you're using npm to develop and publish your code, check out the following help topics:
+.RS 0
+.IP \(bu 4
+json: Make a package.json file. See \fB\fBpackage.json\fR\fR \fI\(la/configuring-npm/package-json\(ra\fR.
+.IP \(bu 4
+link: Links your current working code into Node's path, so that you don't have to reinstall every time you make a change. Use npm help link to do this.
+.IP \(bu 4
+install: It's a good idea to install things if you don't need the symbolic link. Especially, installing other peoples code from the registry is done via npm help install
+.IP \(bu 4
+adduser: Create an account or log in. When you do this, npm will store credentials in the user config file.
+.IP \(bu 4
+publish: Use the npm help publish command to upload your code to the registry.
+.RE 0
+
+.SS "Configuration"
+.P
+npm is extremely configurable. It reads its configuration options from 5 places.
+.RS 0
+.IP \(bu 4
+Command line switches: Set a config with \fB--key val\fR. All keys take a value, even if they are booleans (the config parser doesn't know what the options are at the time of parsing). If you do not provide a value (\fB--key\fR) then the option is set to boolean \fBtrue\fR.
+.IP \(bu 4
+Environment Variables: Set any config by prefixing the name in an environment variable with \fBnpm_config_\fR. For example, \fBexport npm_config_key=val\fR.
+.IP \(bu 4
+User Configs: The file at \fB$HOME/.npmrc\fR is an ini-formatted list of configs. If present, it is parsed. If the \fBuserconfig\fR option is set in the cli or env, that file will be used instead.
+.IP \(bu 4
+Global Configs: The file found at \fB./etc/npmrc\fR (relative to the global prefix will be parsed if it is found. See npm help prefix for more info on the global prefix. If the \fBglobalconfig\fR option is set in the cli, env, or user config, then that file is parsed instead.
+.IP \(bu 4
+Defaults: npm's default configuration options are defined in \fBlib/utils/config/definitions.js\fR. These must not be changed.
+.RE 0
+
+.P
+See npm help config for much much more information.
+.SS "Contributions"
+.P
+Patches welcome!
+.P
+If you would like to help, but don't know what to work on, read the \fBcontributing guidelines\fR \fI\(lahttps://github.com/npm/cli/blob/latest/CONTRIBUTING.md\(ra\fR and check the issues list.
+.SS "Bugs"
+.P
+When you find issues, please report them: \fI\(lahttps://github.com/npm/cli/issues\(ra\fR
+.P
+Please be sure to follow the template and bug reporting guidelines.
+.SS "Feature Requests"
+.P
+Discuss new feature ideas on our discussion forum:
+.RS 0
+.IP \(bu 4
+\fI\(lahttps://github.com/orgs/community/discussions/categories/npm\(ra\fR
+.RE 0
+
+.P
+Or suggest formal RFC proposals:
+.RS 0
+.IP \(bu 4
+\fI\(lahttps://github.com/npm/rfcs\(ra\fR
+.RE 0
+
+.SS "See Also"
+.RS 0
+.IP \(bu 4
+npm help help
+.IP \(bu 4
+\fBpackage.json\fR \fI\(la/configuring-npm/package-json\(ra\fR
+.IP \(bu 4
+npm help npmrc
+.IP \(bu 4
+npm help config
+.IP \(bu 4
+npm help install
+.IP \(bu 4
+npm help prefix
+.IP \(bu 4
+npm help publish
+.RE 0

package/node/node_modules/npm/man/man1/npx.1

@@ -1,156 +1,156 @@
-.TH "NPX" "1" "June 2025" "NPM@10.9.3" ""
-.SH "NAME"
-\fBnpx\fR - Run a command from a local or remote npm package
-.SS "Synopsis"
-.P
-.RS 2
-.nf
-npx -- <pkg>\[lB]@<version>\[rB] \[lB]args...\[rB]
-npx --package=<pkg>\[lB]@<version>\[rB] -- <cmd> \[lB]args...\[rB]
-npx -c '<cmd> \[lB]args...\[rB]'
-npx --package=foo -c '<cmd> \[lB]args...\[rB]'
-.fi
-.RE
-.SS "Description"
-.P
-This command allows you to run an arbitrary command from an npm package (either one installed locally, or fetched remotely), in a similar context as running it via \fBnpm run\fR.
-.P
-Whatever packages are specified by the \fB--package\fR option will be provided in the \fBPATH\fR of the executed command, along with any locally installed package executables. The \fB--package\fR option may be specified multiple times, to execute the supplied command in an environment where all specified packages are available.
-.P
-If any requested packages are not present in the local project dependencies, then they are installed to a folder in the npm cache, which is added to the \fBPATH\fR environment variable in the executed process. A prompt is printed (which can be suppressed by providing either \fB--yes\fR or \fB--no\fR).
-.P
-Package names provided without a specifier will be matched with whatever version exists in the local project. Package names with a specifier will only be considered a match if they have the exact same name and version as the local dependency.
-.P
-If no \fB-c\fR or \fB--call\fR option is provided, then the positional arguments are used to generate the command string. If no \fB--package\fR options are provided, then npm will attempt to determine the executable name from the package specifier provided as the first positional argument according to the following heuristic:
-.RS 0
-.IP \(bu 4
-If the package has a single entry in its \fBbin\fR field in \fBpackage.json\fR, or if all entries are aliases of the same command, then that command will be used.
-.IP \(bu 4
-If the package has multiple \fBbin\fR entries, and one of them matches the unscoped portion of the \fBname\fR field, then that command will be used.
-.IP \(bu 4
-If this does not result in exactly one option (either because there are no bin entries, or none of them match the \fBname\fR of the package), then \fBnpm exec\fR exits with an error.
-.RE 0
-
-.P
-To run a binary \fIother than\fR the named binary, specify one or more \fB--package\fR options, which will prevent npm from inferring the package from the first command argument.
-.SS "\fBnpx\fR vs \fBnpm exec\fR"
-.P
-When run via the \fBnpx\fR binary, all flags and options \fImust\fR be set prior to any positional arguments. When run via \fBnpm exec\fR, a double-hyphen \fB--\fR flag can be used to suppress npm's parsing of switches and options that should be sent to the executed command.
-.P
-For example:
-.P
-.RS 2
-.nf
-$ npx foo@latest bar --package=@npmcli/foo
-.fi
-.RE
-.P
-In this case, npm will resolve the \fBfoo\fR package name, and run the following command:
-.P
-.RS 2
-.nf
-$ foo bar --package=@npmcli/foo
-.fi
-.RE
-.P
-Since the \fB--package\fR option comes \fIafter\fR the positional arguments, it is treated as an argument to the executed command.
-.P
-In contrast, due to npm's argument parsing logic, running this command is different:
-.P
-.RS 2
-.nf
-$ npm exec foo@latest bar --package=@npmcli/foo
-.fi
-.RE
-.P
-In this case, npm will parse the \fB--package\fR option first, resolving the \fB@npmcli/foo\fR package. Then, it will execute the following command in that context:
-.P
-.RS 2
-.nf
-$ foo@latest bar
-.fi
-.RE
-.P
-The double-hyphen character is recommended to explicitly tell npm to stop parsing command line options and switches. The following command would thus be equivalent to the \fBnpx\fR command above:
-.P
-.RS 2
-.nf
-$ npm exec -- foo@latest bar --package=@npmcli/foo
-.fi
-.RE
-.SS "Examples"
-.P
-Run the version of \fBtap\fR in the local dependencies, with the provided arguments:
-.P
-.RS 2
-.nf
-$ npm exec -- tap --bail test/foo.js
-$ npx tap --bail test/foo.js
-.fi
-.RE
-.P
-Run a command \fIother than\fR the command whose name matches the package name by specifying a \fB--package\fR option:
-.P
-.RS 2
-.nf
-$ npm exec --package=foo -- bar --bar-argument
-# ~ or ~
-$ npx --package=foo bar --bar-argument
-.fi
-.RE
-.P
-Run an arbitrary shell script, in the context of the current project:
-.P
-.RS 2
-.nf
-$ npm x -c 'eslint && say "hooray, lint passed"'
-$ npx -c 'eslint && say "hooray, lint passed"'
-.fi
-.RE
-.SS "Compatibility with Older npx Versions"
-.P
-The \fBnpx\fR binary was rewritten in npm v7.0.0, and the standalone \fBnpx\fR package deprecated at that time. \fBnpx\fR uses the \fBnpm exec\fR command instead of a separate argument parser and install process, with some affordances to maintain backwards compatibility with the arguments it accepted in previous versions.
-.P
-This resulted in some shifts in its functionality:
-.RS 0
-.IP \(bu 4
-Any \fBnpm\fR config value may be provided.
-.IP \(bu 4
-To prevent security and user-experience problems from mistyping package names, \fBnpx\fR prompts before installing anything. Suppress this prompt with the \fB-y\fR or \fB--yes\fR option.
-.IP \(bu 4
-The \fB--no-install\fR option is deprecated, and will be converted to \fB--no\fR.
-.IP \(bu 4
-Shell fallback functionality is removed, as it is not advisable.
-.IP \(bu 4
-The \fB-p\fR argument is a shorthand for \fB--parseable\fR in npm, but shorthand for \fB--package\fR in npx. This is maintained, but only for the \fBnpx\fR executable.
-.IP \(bu 4
-The \fB--ignore-existing\fR option is removed. Locally installed bins are always present in the executed process \fBPATH\fR.
-.IP \(bu 4
-The \fB--npm\fR option is removed. \fBnpx\fR will always use the \fBnpm\fR it ships with.
-.IP \(bu 4
-The \fB--node-arg\fR and \fB-n\fR options have been removed. Use \fB\fBNODE_OPTIONS\fR\fR \fI\(lahttps://nodejs.org/api/cli.html#node_optionsoptions\(ra\fR instead: e.g., \fBNODE_OPTIONS="--trace-warnings --trace-exit" npx foo --random=true\fR
-.IP \(bu 4
-The \fB--always-spawn\fR option is redundant, and thus removed.
-.IP \(bu 4
-The \fB--shell\fR option is replaced with \fB--script-shell\fR, but maintained in the \fBnpx\fR executable for backwards compatibility.
-.RE 0
-
-.SS "See Also"
-.RS 0
-.IP \(bu 4
-npm help run-script
-.IP \(bu 4
-npm help scripts
-.IP \(bu 4
-npm help test
-.IP \(bu 4
-npm help start
-.IP \(bu 4
-npm help restart
-.IP \(bu 4
-npm help stop
-.IP \(bu 4
-npm help config
-.IP \(bu 4
-npm help exec
-.RE 0
+.TH "NPX" "1" "June 2025" "NPM@10.9.3" ""
+.SH "NAME"
+\fBnpx\fR - Run a command from a local or remote npm package
+.SS "Synopsis"
+.P
+.RS 2
+.nf
+npx -- <pkg>\[lB]@<version>\[rB] \[lB]args...\[rB]
+npx --package=<pkg>\[lB]@<version>\[rB] -- <cmd> \[lB]args...\[rB]
+npx -c '<cmd> \[lB]args...\[rB]'
+npx --package=foo -c '<cmd> \[lB]args...\[rB]'
+.fi
+.RE
+.SS "Description"
+.P
+This command allows you to run an arbitrary command from an npm package (either one installed locally, or fetched remotely), in a similar context as running it via \fBnpm run\fR.
+.P
+Whatever packages are specified by the \fB--package\fR option will be provided in the \fBPATH\fR of the executed command, along with any locally installed package executables. The \fB--package\fR option may be specified multiple times, to execute the supplied command in an environment where all specified packages are available.
+.P
+If any requested packages are not present in the local project dependencies, then they are installed to a folder in the npm cache, which is added to the \fBPATH\fR environment variable in the executed process. A prompt is printed (which can be suppressed by providing either \fB--yes\fR or \fB--no\fR).
+.P
+Package names provided without a specifier will be matched with whatever version exists in the local project. Package names with a specifier will only be considered a match if they have the exact same name and version as the local dependency.
+.P
+If no \fB-c\fR or \fB--call\fR option is provided, then the positional arguments are used to generate the command string. If no \fB--package\fR options are provided, then npm will attempt to determine the executable name from the package specifier provided as the first positional argument according to the following heuristic:
+.RS 0
+.IP \(bu 4
+If the package has a single entry in its \fBbin\fR field in \fBpackage.json\fR, or if all entries are aliases of the same command, then that command will be used.
+.IP \(bu 4
+If the package has multiple \fBbin\fR entries, and one of them matches the unscoped portion of the \fBname\fR field, then that command will be used.
+.IP \(bu 4
+If this does not result in exactly one option (either because there are no bin entries, or none of them match the \fBname\fR of the package), then \fBnpm exec\fR exits with an error.
+.RE 0
+
+.P
+To run a binary \fIother than\fR the named binary, specify one or more \fB--package\fR options, which will prevent npm from inferring the package from the first command argument.
+.SS "\fBnpx\fR vs \fBnpm exec\fR"
+.P
+When run via the \fBnpx\fR binary, all flags and options \fImust\fR be set prior to any positional arguments. When run via \fBnpm exec\fR, a double-hyphen \fB--\fR flag can be used to suppress npm's parsing of switches and options that should be sent to the executed command.
+.P
+For example:
+.P
+.RS 2
+.nf
+$ npx foo@latest bar --package=@npmcli/foo
+.fi
+.RE
+.P
+In this case, npm will resolve the \fBfoo\fR package name, and run the following command:
+.P
+.RS 2
+.nf
+$ foo bar --package=@npmcli/foo
+.fi
+.RE
+.P
+Since the \fB--package\fR option comes \fIafter\fR the positional arguments, it is treated as an argument to the executed command.
+.P
+In contrast, due to npm's argument parsing logic, running this command is different:
+.P
+.RS 2
+.nf
+$ npm exec foo@latest bar --package=@npmcli/foo
+.fi
+.RE
+.P
+In this case, npm will parse the \fB--package\fR option first, resolving the \fB@npmcli/foo\fR package. Then, it will execute the following command in that context:
+.P
+.RS 2
+.nf
+$ foo@latest bar
+.fi
+.RE
+.P
+The double-hyphen character is recommended to explicitly tell npm to stop parsing command line options and switches. The following command would thus be equivalent to the \fBnpx\fR command above:
+.P
+.RS 2
+.nf
+$ npm exec -- foo@latest bar --package=@npmcli/foo
+.fi
+.RE
+.SS "Examples"
+.P
+Run the version of \fBtap\fR in the local dependencies, with the provided arguments:
+.P
+.RS 2
+.nf
+$ npm exec -- tap --bail test/foo.js
+$ npx tap --bail test/foo.js
+.fi
+.RE
+.P
+Run a command \fIother than\fR the command whose name matches the package name by specifying a \fB--package\fR option:
+.P
+.RS 2
+.nf
+$ npm exec --package=foo -- bar --bar-argument
+# ~ or ~
+$ npx --package=foo bar --bar-argument
+.fi
+.RE
+.P
+Run an arbitrary shell script, in the context of the current project:
+.P
+.RS 2
+.nf
+$ npm x -c 'eslint && say "hooray, lint passed"'
+$ npx -c 'eslint && say "hooray, lint passed"'
+.fi
+.RE
+.SS "Compatibility with Older npx Versions"
+.P
+The \fBnpx\fR binary was rewritten in npm v7.0.0, and the standalone \fBnpx\fR package deprecated at that time. \fBnpx\fR uses the \fBnpm exec\fR command instead of a separate argument parser and install process, with some affordances to maintain backwards compatibility with the arguments it accepted in previous versions.
+.P
+This resulted in some shifts in its functionality:
+.RS 0
+.IP \(bu 4
+Any \fBnpm\fR config value may be provided.
+.IP \(bu 4
+To prevent security and user-experience problems from mistyping package names, \fBnpx\fR prompts before installing anything. Suppress this prompt with the \fB-y\fR or \fB--yes\fR option.
+.IP \(bu 4
+The \fB--no-install\fR option is deprecated, and will be converted to \fB--no\fR.
+.IP \(bu 4
+Shell fallback functionality is removed, as it is not advisable.
+.IP \(bu 4
+The \fB-p\fR argument is a shorthand for \fB--parseable\fR in npm, but shorthand for \fB--package\fR in npx. This is maintained, but only for the \fBnpx\fR executable.
+.IP \(bu 4
+The \fB--ignore-existing\fR option is removed. Locally installed bins are always present in the executed process \fBPATH\fR.
+.IP \(bu 4
+The \fB--npm\fR option is removed. \fBnpx\fR will always use the \fBnpm\fR it ships with.
+.IP \(bu 4
+The \fB--node-arg\fR and \fB-n\fR options have been removed. Use \fB\fBNODE_OPTIONS\fR\fR \fI\(lahttps://nodejs.org/api/cli.html#node_optionsoptions\(ra\fR instead: e.g., \fBNODE_OPTIONS="--trace-warnings --trace-exit" npx foo --random=true\fR
+.IP \(bu 4
+The \fB--always-spawn\fR option is redundant, and thus removed.
+.IP \(bu 4
+The \fB--shell\fR option is replaced with \fB--script-shell\fR, but maintained in the \fBnpx\fR executable for backwards compatibility.
+.RE 0
+
+.SS "See Also"
+.RS 0
+.IP \(bu 4
+npm help run-script
+.IP \(bu 4
+npm help scripts
+.IP \(bu 4
+npm help test
+.IP \(bu 4
+npm help start
+.IP \(bu 4
+npm help restart
+.IP \(bu 4
+npm help stop
+.IP \(bu 4
+npm help config
+.IP \(bu 4
+npm help exec
+.RE 0