FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

deps: upgrade npm to 8.0.0 · nodejs/node@b89c7ae · GitHub

deps: upgrade npm to 8.0.0 · nodejs/node@b89c7ae · GitHub
Skip to content

Navigation Menu

Sign in
Sign in
Sign up

Commit b89c7ae

Browse files
npm-robot
authored and
danielleadams
committed
deps: upgrade npm to 8.0.0
PR-URL: #40369 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Danielle Adams <adamzdanielle@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
1 parent 8d1c471 commit b89c7ae

748 files changed

Lines changed: 4610 additions & 97661 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎deps/npm/docs/content/configuring-npm/package-lock-json.md‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -138,7 +138,8 @@ Package descriptors have the following fields:
138138
the case of packages fetched from the registry, this will be a url to a
139139
tarball. In the case of git dependencies, this will be the full git url
140140
with commit sha. In the case of link dependencies, this will be the
141-
location of the link target.
141+
location of the link target. `registry.npmjs.org` is a magic value meaning
142+
"the currently configured registry".
142143

143144
* integrity: A `sha512` or `sha1` [Standard Subresource
144145
Integrity](https://w3c.github.io/webappsec/specs/subresourceintegrity/)
@@ -201,7 +202,8 @@ Dependency objects have the following fields:
201202

202203
* resolved: For registry sources this is path of the tarball relative to
203204
the registry URL. If the tarball URL isn't on the same server as the
204-
registry URL then this is a complete URL.
205+
registry URL then this is a complete URL. `registry.npmjs.org` is a magic
206+
value meaning "the currently configured registry".
205207

206208
* bundled: If true, this is the bundled dependency and will be installed
207209
by the parent module. When installing, this module will be extracted

‎deps/npm/docs/content/using-npm/registry.md‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,13 @@ The registry URL used is determined by the scope of the package (see
3030
supplied by the `registry` config parameter. See [`npm config`](/commands/npm-config),
3131
[`npmrc`](/configuring-npm/npmrc), and [`config`](/using-npm/config) for more on managing npm's configuration.
3232

33+
When the default registry is used in a package-lock or shrinkwrap is has the
34+
special meaning of "the currently configured registry". If you create a lock
35+
file while using the default registry you can switch to another registry and
36+
npm will install packages from the new registry, but if you create a lock
37+
file while using a custom registry packages will be installed from that
38+
registry even after you change to another registry.
39+
3340
### Does npm send any information about me back to the registry?
3441

3542
Yes.

‎deps/npm/docs/content/using-npm/scope.md‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,8 @@ desired, with `npm access` or on the npmjs.com website.
9898

9999
Scopes can be associated with a separate registry. This allows you to
100100
seamlessly use a mix of packages from the primary npm registry and one or more
101-
private registries, such as npm Enterprise.
101+
private registries, such as [GitHub Packages](https://github.com/features/packages) or the open source [Verdaccio](https://verdaccio.org)
102+
project.
102103

103104
You can associate a scope with a registry at login, e.g.
104105

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

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -176,6 +176,22 @@ npm run test --workspaces
176176

177177
Will run the `test` script in both `./packages/a` and `./packages/b`.
178178

179+
Commands will be run in each workspace in the order they appear in your `package.json`
180+
181+
```
182+
{
183+
"workspaces": [ "packages/a", "packages/b" ]
184+
}
185+
```
186+
187+
Order of run is different with:
188+
189+
```
190+
{
191+
"workspaces": [ "packages/b", "packages/a" ]
192+
}
193+
```
194+
179195
### Ignoring missing scripts
180196

181197
It is not required for all of the workspaces to implement scripts run with the `npm run` command.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -159,7 +159,7 @@ <h3 id="description">Description</h3>
159159
the results to only the paths to the packages named. Note that nested
160160
packages will <em>also</em> show the paths to the specified packages. For
161161
example, running <code>npm ls promzard</code> in npm’s source tree will show:</p>
162-
<pre lang="bash"><code>npm@7.24.0 /path/to/npm
162+
<pre lang="bash"><code>npm@8.0.0 /path/to/npm
163163
└─┬ init-package-json@0.0.4
164164
└── promzard@0.1.5
165165
</code></pre>

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -148,7 +148,7 @@ <h2 id="table-of-contents">Table of contents</h2>
148148
<pre lang="bash"><code>npm &lt;command&gt; [args]
149149
</code></pre>
150150
<h3 id="version">Version</h3>
151-
<p>7.24.0</p>
151+
<p>8.0.0</p>
152152
<h3 id="description">Description</h3>
153153
<p>npm is the package manager for the Node JavaScript platform. It puts
154154
modules in place so that node can find them, and manages dependency

‎deps/npm/docs/output/configuring-npm/package-lock-json.html‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -262,7 +262,8 @@ <h4 id="packages"><code>packages</code></h4>
262262
the case of packages fetched from the registry, this will be a url to a
263263
tarball. In the case of git dependencies, this will be the full git url
264264
with commit sha. In the case of link dependencies, this will be the
265-
location of the link target.</p>
265+
location of the link target. <code>registry.npmjs.org</code> is a magic value meaning
266+
“the currently configured registry”.</p>
266267
</li>
267268
<li>
268269
<p>integrity: A <code>sha512</code> or <code>sha1</code> <a href="https://w3c.github.io/webappsec/specs/subresourceintegrity/">Standard Subresource
@@ -334,7 +335,8 @@ <h4 id="dependencies">dependencies</h4>
334335
<li>
335336
<p>resolved: For registry sources this is path of the tarball relative to
336337
the registry URL. If the tarball URL isn’t on the same server as the
337-
registry URL then this is a complete URL.</p>
338+
registry URL then this is a complete URL. <code>registry.npmjs.org</code> is a magic
339+
value meaning “the currently configured registry”.</p>
338340
</li>
339341
<li>
340342
<p>bundled: If true, this is the bundled dependency and will be installed

‎deps/npm/docs/output/using-npm/registry.html‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -163,6 +163,12 @@ <h2 id="table-of-contents">Table of contents</h2>
163163
<a href="../using-npm/scope.html"><code>scope</code></a>. If no scope is specified, the default registry is used, which is
164164
supplied by the <code>registry</code> config parameter. See <a href="../commands/npm-config.html"><code>npm config</code></a>,
165165
<a href="../configuring-npm/npmrc.html"><code>npmrc</code></a>, and <a href="../using-npm/config.html"><code>config</code></a> for more on managing npm’s configuration.</p>
166+
<p>When the default registry is used in a package-lock or shrinkwrap is has the
167+
special meaning of “the currently configured registry”. If you create a lock
168+
file while using the default registry you can switch to another registry and
169+
npm will install packages from the new registry, but if you create a lock
170+
file while using a custom registry packages will be installed from that
171+
registry even after you change to another registry.</p>
166172
<h3 id="does-npm-send-any-information-about-me-back-to-the-registry">Does npm send any information about me back to the registry?</h3>
167173
<p>Yes.</p>
168174
<p>When making requests of the registry npm adds two headers with information

‎deps/npm/docs/output/using-npm/scope.html‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -206,7 +206,8 @@ <h4 id="publishing-private-scoped-packages-to-the-npm-registry">Publishing priva
206206
<h3 id="associating-a-scope-with-a-registry">Associating a scope with a registry</h3>
207207
<p>Scopes can be associated with a separate registry. This allows you to
208208
seamlessly use a mix of packages from the primary npm registry and one or more
209-
private registries, such as npm Enterprise.</p>
209+
private registries, such as <a href="https://github.com/features/packages">GitHub Packages</a> or the open source <a href="https://verdaccio.org">Verdaccio</a>
210+
project.</p>
210211
<p>You can associate a scope with a registry at login, e.g.</p>
211212
<pre lang="bash"><code>npm login --registry=http://reg.example.com --scope=@myco
212213
</code></pre>

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

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -264,6 +264,16 @@ <h3 id="running-commands-in-the-context-of-workspaces">Running commands in the c
264264
<pre><code>npm run test --workspaces
265265
</code></pre>
266266
<p>Will run the <code>test</code> script in both <code>./packages/a</code> and <code>./packages/b</code>.</p>
267+
<p>Commands will be run in each workspace in the order they appear in your <code>package.json</code></p>
268+
<pre><code>{
269+
"workspaces": [ "packages/a", "packages/b" ]
270+
}
271+
</code></pre>
272+
<p>Order of run is different with:</p>
273+
<pre><code>{
274+
"workspaces": [ "packages/b", "packages/a" ]
275+
}
276+
</code></pre>
267277
<h3 id="ignoring-missing-scripts">Ignoring missing scripts</h3>
268278
<p>It is not required for all of the workspaces to implement scripts run with the <code>npm run</code> command.</p>
269279
<p>By running the command with the <code>--if-present</code> flag, npm will ignore workspaces missing target script.</p>

0 commit comments

Comments
 (0)

Footer

© 2026 GitHub, Inc.
Back | FazBrowse Home | New Git URL