deps: upgrade npm to 8.5.1

PR-URL: #42039
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Mestery <mestery@protonmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>

Author: npm-robot

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

@@ -78,11 +78,20 @@ into a tarball (b).
 
 * `npm install <folder>`:
 
-    Install the package in the directory as a symlink in the current
-    project.  Its dependencies will be installed before it's linked. If
-    `<folder>` sits inside the root of your project, its dependencies may
+    If `<folder>` sits inside the root of your project, its dependencies will be installed and may
     be hoisted to the top-level `node_modules` as they would for other
-    types of dependencies.
+    types of dependencies. If `<folder>` sits outside the root of your project,
+    *npm will not install the package dependencies* in the directory `<folder>`,
+    but it will create a symlink to `<folder>`.
+
+    > NOTE: If you want to install the content of a directory like a package from the registry instead of creating a link, you would need to use [`npm pack`](/commands/npm-pack) while in the `<folder>` directory, and then install the resulting tarball instead of the `<folder>` using `npm install <tarball file>`
+
+    Example:
+
+    ```bash
+    npm install ../../other-package
+    npm install ./sub-package
+    ```
 
 * `npm install <tarball file>`:
 

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

@@ -18,11 +18,14 @@ Ping the configured or given npm registry and verify authentication.
 If it works it will output something like:
 
 ```bash
-Ping success: {*Details about registry*}
+npm notice PING https://registry.npmjs.org/
+npm notice PONG 255ms
 ```
-otherwise you will get:
+otherwise you will get an error:
 ```bash
-Ping error: {*Detail about error}
+npm notice PING http://foo.com/
+npm ERR! code E404
+npm ERR! 404 Not Found - GET http://www.foo.com/-/ping?write=true
 ```
 
 ### Configuration

deps/npm/docs/content/using-npm/workspaces.md

@@ -30,24 +30,25 @@ Workspaces are usually defined via the `workspaces` property of the
 {
   "name": "my-workspaces-powered-project",
   "workspaces": [
-    "workspace-a"
+    "packages/a"
   ]
 }
 ```
 
 Given the above `package.json` example living at a current working
-directory `.` that contains a folder named `workspace-a` that itself contains
+directory `.` that contains a folder named `packages/a` that itself contains
 a `package.json` inside it, defining a Node.js package, e.g:
 
 ```
 .
 +-- package.json
-`-- workspace-a
-   `-- package.json
+`-- packages
+   +-- a
+   |   `-- package.json
 ```
 
 The expected result once running `npm install` in this current working
-directory `.` is that the folder `workspace-a` will get symlinked to the
+directory `.` is that the folder `packages/a` will get symlinked to the
 `node_modules` folder of the current working dir.
 
 Below is a post `npm install` example, given that same previous example
@@ -56,11 +57,12 @@ structure of files and folders:
 ```
 .
 +-- node_modules
-|  `-- workspace-a -> ../workspace-a
+|  `-- packages/a -> ../packages/a
 +-- package-lock.json
 +-- package.json
-`-- workspace-a
-   `-- package.json
+`-- packages
+   +-- a
+   |   `-- package.json
 ```
 
 ### Getting started with workspaces

deps/npm/docs/output/commands/npm-install.html

@@ -211,11 +211,18 @@ <h3 id="description">Description</h3>
 </li>
 <li>
 <p><code>npm install &lt;folder&gt;</code>:</p>
-<p>Install the package in the directory as a symlink in the current
-project.  Its dependencies will be installed before it's linked. If
-<code>&lt;folder&gt;</code> sits inside the root of your project, its dependencies may
+<p>If <code>&lt;folder&gt;</code> sits inside the root of your project, its dependencies will be installed and may
 be hoisted to the top-level <code>node_modules</code> as they would for other
-types of dependencies.</p>
+types of dependencies. If <code>&lt;folder&gt;</code> sits outside the root of your project,
+<em>npm will not install the package dependencies</em> in the directory <code>&lt;folder&gt;</code>,
+but it will create a symlink to <code>&lt;folder&gt;</code>.</p>
+<blockquote>
+<p>NOTE: If you want to install the content of a directory like a package from the registry instead of creating a link, you would need to use <a href="../commands/npm-pack.html"><code>npm pack</code></a> while in the <code>&lt;folder&gt;</code> directory, and then install the resulting tarball instead of the <code>&lt;folder&gt;</code> using <code>npm install &lt;tarball file&gt;</code></p>
+</blockquote>
+<p>Example:</p>
+<pre lang="bash"><code>npm install ../../other-package
+npm install ./sub-package
+</code></pre>
 </li>
 <li>
 <p><code>npm install &lt;tarball file&gt;</code>:</p>

deps/npm/docs/output/commands/npm-ls.html

@@ -160,7 +160,7 @@ <h3 id="description">Description</h3>
 the results to only the paths to the packages named.  Note that nested
 packages will <em>also</em> show the paths to the specified packages.  For
 example, running <code>npm ls promzard</code> in npm's source tree will show:</p>
-<pre lang="bash"><code>npm@8.5.0 /path/to/npm
+<pre lang="bash"><code>npm@8.5.1 /path/to/npm
 └─┬ init-package-json@0.0.4
   └── promzard@0.1.5
 </code></pre>

deps/npm/docs/output/commands/npm-ping.html

@@ -152,10 +152,13 @@ <h2 id="table-of-contents">Table of contents</h2>
 <h3 id="description">Description</h3>
 <p>Ping the configured or given npm registry and verify authentication.
 If it works it will output something like:</p>
-<pre lang="bash"><code>Ping success: {*Details about registry*}
+<pre lang="bash"><code>npm notice PING https://registry.npmjs.org/
+npm notice PONG 255ms
 </code></pre>
-<p>otherwise you will get:</p>
-<pre lang="bash"><code>Ping error: {*Detail about error}
+<p>otherwise you will get an error:</p>
+<pre lang="bash"><code>npm notice PING http://foo.com/
+npm ERR! code E404
+npm ERR! 404 Not Found - GET http://www.foo.com/-/ping?write=true
 </code></pre>
 <h3 id="configuration">Configuration</h3>
 <!-- raw HTML omitted -->

deps/npm/docs/output/commands/npm.html

@@ -149,7 +149,7 @@ <h2 id="table-of-contents">Table of contents</h2>
 <pre lang="bash"><code>npm &lt;command&gt; [args]
 </code></pre>
 <h3 id="version">Version</h3>
-<p>8.5.0</p>
+<p>8.5.1</p>
 <h3 id="description">Description</h3>
 <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

deps/npm/docs/output/using-npm/workspaces.html

@@ -164,30 +164,32 @@ <h3 id="defining-workspaces">Defining workspaces</h3>
 <pre lang="json"><code>{
   "name": "my-workspaces-powered-project",
   "workspaces": [
-    "workspace-a"
+    "packages/a"
   ]
 }
 </code></pre>
 <p>Given the above <code>package.json</code> example living at a current working
-directory <code>.</code> that contains a folder named <code>workspace-a</code> that itself contains
+directory <code>.</code> that contains a folder named <code>packages/a</code> that itself contains
 a <code>package.json</code> inside it, defining a Node.js package, e.g:</p>
 <pre><code>.
 +-- package.json
-`-- workspace-a
-   `-- package.json
+`-- packages
+   +-- a
+   |   `-- package.json
 </code></pre>
 <p>The expected result once running <code>npm install</code> in this current working
-directory <code>.</code> is that the folder <code>workspace-a</code> will get symlinked to the
+directory <code>.</code> is that the folder <code>packages/a</code> will get symlinked to the
 <code>node_modules</code> folder of the current working dir.</p>
 <p>Below is a post <code>npm install</code> example, given that same previous example
 structure of files and folders:</p>
 <pre><code>.
 +-- node_modules
-|  `-- workspace-a -&gt; ../workspace-a
+|  `-- packages/a -&gt; ../packages/a
 +-- package-lock.json
 +-- package.json
-`-- workspace-a
-   `-- package.json
+`-- packages
+   +-- a
+   |   `-- package.json
 </code></pre>
 <h3 id="getting-started-with-workspaces">Getting started with workspaces</h3>
 <p>You may automate the required steps to define a new workspace using

deps/npm/lib/commands/pkg.js

@@ -9,6 +9,8 @@ class Pkg extends BaseCommand {
     'set <key>=<value> [<key>=<value> ...]',
     'get [<key> [<key> ...]]',
     'delete <key> [<key> ...]',
+    'set [<array>[<index>].<key>=<value> ...]',
+    'set [<array>[].<key>=<value> ...]',
   ]
 
   static params = [

deps/npm/man/man1/npm-install.1

@@ -87,11 +87,23 @@ NOTE: The \fB\-\-production\fP flag has no particular meaning when adding a
 .
 .IP \(bu 2
 \fBnpm install <folder>\fP:
-  Install the package in the directory as a symlink in the current
-  project\.  Its dependencies will be installed before it's linked\. If
-  \fB<folder>\fP sits inside the root of your project, its dependencies may
+  If \fB<folder>\fP sits inside the root of your project, its dependencies will be installed and may
   be hoisted to the top\-level \fBnode_modules\fP as they would for other
-  types of dependencies\.
+  types of dependencies\. If \fB<folder>\fP sits outside the root of your project,
+  \fInpm will not install the package dependencies\fR in the directory \fB<folder>\fP,
+  but it will create a symlink to \fB<folder>\fP\|\.
+.QP
+NOTE: If you want to install the content of a directory like a package from the registry instead of creating a link, you would need to use npm help \fBpack\fP while in the \fB<folder>\fP directory, and then install the resulting tarball instead of the \fB<folder>\fP using \fBnpm install <tarball file>\fP
+
+.
+  Example:
+.P
+.RS 2
+.nf
+  npm install \.\./\.\./other\-package
+  npm install \./sub\-package
+.fi
+.RE
 .IP \(bu 2
 \fBnpm install <tarball file>\fP:
   Install a package that is sitting on the filesystem\.  Note: if you just

deps/npm/man/man1/npm-ls.1

@@ -26,7 +26,7 @@ example, running \fBnpm ls promzard\fP in npm's source tree will show:
 .P
 .RS 2
 .nf
-npm@8\.5\.0 /path/to/npm
+npm@8\.5\.1 /path/to/npm
 └─┬ init\-package\-json@0\.0\.4
   └── promzard@0\.1\.5
 .fi

deps/npm/man/man1/npm-ping.1

@@ -17,15 +17,18 @@ If it works it will output something like:
 .P
 .RS 2
 .nf
-Ping success: {*Details about registry*}
+npm notice PING https://registry\.npmjs\.org/
+npm notice PONG 255ms
 .fi
 .RE
 .P
-otherwise you will get:
+otherwise you will get an error:
 .P
 .RS 2
 .nf
-Ping error: {*Detail about error}
+npm notice PING http://foo\.com/
+npm ERR! code E404
+npm ERR! 404 Not Found \- GET http://www\.foo\.com/\-/ping?write=true
 .fi
 .RE
 .SS Configuration

deps/npm/man/man1/npm.1

@@ -10,7 +10,7 @@ npm <command> [args]
 .RE
 .SS Version
 .P
-8\.5\.0
+8\.5\.1
 .SS Description
 .P
 npm is the package manager for the Node JavaScript platform\.  It puts

deps/npm/man/man7/workspaces.7

@@ -27,27 +27,28 @@ npm help \fBpackage\.json\fP file, e\.g:
 {
   "name": "my\-workspaces\-powered\-project",
   "workspaces": [
-    "workspace\-a"
+    "packages/a"
   ]
 }
 .fi
 .RE
 .P
 Given the above \fBpackage\.json\fP example living at a current working
-directory \fB\|\.\fP that contains a folder named \fBworkspace\-a\fP that itself contains
+directory \fB\|\.\fP that contains a folder named \fBpackages/a\fP that itself contains
 a \fBpackage\.json\fP inside it, defining a Node\.js package, e\.g:
 .P
 .RS 2
 .nf
 \|\.
 +\-\- package\.json
-`\-\- workspace\-a
-   `\-\- package\.json
+`\-\- packages
+   +\-\- a
+   |   `\-\- package\.json
 .fi
 .RE
 .P
 The expected result once running \fBnpm install\fP in this current working
-directory \fB\|\.\fP is that the folder \fBworkspace\-a\fP will get symlinked to the
+directory \fB\|\.\fP is that the folder \fBpackages/a\fP will get symlinked to the
 \fBnode_modules\fP folder of the current working dir\.
 .P
 Below is a post \fBnpm install\fP example, given that same previous example
@@ -57,11 +58,12 @@ structure of files and folders:
 .nf
 \|\.
 +\-\- node_modules
-|  `\-\- workspace\-a \-> \.\./workspace\-a
+|  `\-\- packages/a \-> \.\./packages/a
 +\-\- package\-lock\.json
 +\-\- package\.json
-`\-\- workspace\-a
-   `\-\- package\.json
+`\-\- packages
+   +\-\- a
+   |   `\-\- package\.json
 .fi
 .RE
 .SS Getting started with workspaces