deps: upgrade npm to 11.1.0

deps/npm/README.md

@@ -1,16 +1,8 @@
 # npm - a JavaScript package manager
 
-[![npm version](https://img.shields.io/npm/v/npm.svg)](https://npm.im/npm)
-[![license](https://img.shields.io/npm/l/npm.svg)](https://npm.im/npm)
-[![CI - cli](https://github.com/npm/cli/actions/workflows/ci.yml/badge.svg)](https://github.com/npm/cli/actions/workflows/ci.yml)
-[![Benchmark Suite](https://github.com/npm/cli/actions/workflows/benchmark.yml/badge.svg)](https://github.com/npm/cli/actions/workflows/benchmark.yml)
-
 ### Requirements
 
-One of the following versions of [Node.js](https://nodejs.org/en/download/) must be installed to run **`npm`**:
-
-* `18.x.x` >= `18.17.0`
-* `20.5.0` or higher
+You should be running a currently supported version of [Node.js](https://nodejs.org/en/download/) to run **`npm`**.  For a list of which versions of Node.js are currently supported, please see the [Node.js releases](https://nodejs.org/en/about/previous-releases) page.
 
 ### Installation
 

deps/npm/docs/content/commands/npm-deprecate.md

@@ -64,6 +64,21 @@ password, npm will prompt on the command line for one.
 
 
 
+#### `dry-run`
+
+* Default: false
+* Type: Boolean
+
+Indicates that you don't want npm to make any changes and that it should
+only report what it would have done. This can be passed into any of the
+commands that modify your local installation, eg, `install`, `update`,
+`dedupe`, `uninstall`, as well as `pack` and `publish`.
+
+Note: This is NOT honored by other network related commands, eg `dist-tags`,
+`owner`, etc.
+
+
+
 ### See Also
 
 * [package spec](/using-npm/package-spec)

deps/npm/docs/content/commands/npm-ls.md

@@ -27,7 +27,7 @@ packages will *also* show the paths to the specified packages.  For
 example, running `npm ls promzard` in npm's source tree will show:
 
 ```bash
-npm@11.0.0 /path/to/npm
+npm@11.1.0 /path/to/npm
 └─┬ [email protected]
   └── [email protected]
 ```
@@ -107,7 +107,7 @@ folder instead of the current working directory. See
 
 #### `depth`
 
-* Default: `Infinity` if `--all` is set, otherwise `1`
+* Default: `Infinity` if `--all` is set, otherwise `0`
 * Type: null or Number
 
 The depth to go when recursing packages for `npm ls`.

deps/npm/docs/content/commands/npm-undeprecate.md

@@ -0,0 +1,63 @@
+---
+title: npm-undeprecate
+section: 1
+description: Undeprecate a version of a package
+---
+
+### Synopsis
+
+```bash
+npm undeprecate <package-spec>
+```
+
+Note: This command is unaware of workspaces.
+
+### Description
+
+This command will update the npm registry entry for a package, removing any
+deprecation warnings that currently exist.
+
+It works in the same way as [npm deprecate](/commands/npm-deprecate), except
+that this command removes deprecation warnings instead of adding them.
+
+### Configuration
+
+#### `registry`
+
+* Default: "https://registry.npmjs.org/"
+* Type: URL
+
+The base URL of the npm registry.
+
+
+
+#### `otp`
+
+* Default: null
+* Type: null or String
+
+This is a one-time password from a two-factor authenticator. It's needed
+when publishing or changing package permissions with `npm access`.
+
+If not set, and a registry response fails with a challenge for a one-time
+password, npm will prompt on the command line for one.
+
+
+
+#### `dry-run`
+
+* Default: false
+* Type: Boolean
+
+Indicates that you don't want npm to make any changes and that it should
+only report what it would have done. This can be passed into any of the
+commands that modify your local installation, eg, `install`, `update`,
+`dedupe`, `uninstall`, as well as `pack` and `publish`.
+
+Note: This is NOT honored by other network related commands, eg `dist-tags`,
+`owner`, etc.
+
+
+### See Also
+
+* [npm deprecate](/commands/npm-deprecate)

deps/npm/docs/content/commands/npm.md

@@ -14,7 +14,7 @@ Note: This command is unaware of workspaces.
 
 ### Version
 
-11.0.0
+11.1.0
 
 ### Description