diff options
Diffstat (limited to 'deps/npm/docs')
-rw-r--r-- | deps/npm/docs/content/configuring-npm/package-lock-json.md | 6 | ||||
-rw-r--r-- | deps/npm/docs/content/using-npm/registry.md | 7 | ||||
-rw-r--r-- | deps/npm/docs/content/using-npm/scope.md | 3 | ||||
-rw-r--r-- | deps/npm/docs/content/using-npm/workspaces.md | 16 | ||||
-rw-r--r-- | deps/npm/docs/output/commands/npm-ls.html | 2 | ||||
-rw-r--r-- | deps/npm/docs/output/commands/npm.html | 2 | ||||
-rw-r--r-- | deps/npm/docs/output/configuring-npm/package-lock-json.html | 6 | ||||
-rw-r--r-- | deps/npm/docs/output/using-npm/registry.html | 6 | ||||
-rw-r--r-- | deps/npm/docs/output/using-npm/scope.html | 3 | ||||
-rw-r--r-- | deps/npm/docs/output/using-npm/workspaces.html | 10 |
10 files changed, 53 insertions, 8 deletions
diff --git a/deps/npm/docs/content/configuring-npm/package-lock-json.md b/deps/npm/docs/content/configuring-npm/package-lock-json.md index 9b126867b80..61766dea355 100644 --- a/deps/npm/docs/content/configuring-npm/package-lock-json.md +++ b/deps/npm/docs/content/configuring-npm/package-lock-json.md @@ -138,7 +138,8 @@ Package descriptors have the following fields: the case of packages fetched from the registry, this will be a url to a tarball. In the case of git dependencies, this will be the full git url with commit sha. In the case of link dependencies, this will be the - location of the link target. + location of the link target. `registry.npmjs.org` is a magic value meaning + "the currently configured registry". * integrity: A `sha512` or `sha1` [Standard Subresource Integrity](https://w3c.github.io/webappsec/specs/subresourceintegrity/) @@ -201,7 +202,8 @@ Dependency objects have the following fields: * resolved: For registry sources this is path of the tarball relative to the registry URL. If the tarball URL isn't on the same server as the - registry URL then this is a complete URL. + registry URL then this is a complete URL. `registry.npmjs.org` is a magic + value meaning "the currently configured registry". * bundled: If true, this is the bundled dependency and will be installed by the parent module. When installing, this module will be extracted diff --git a/deps/npm/docs/content/using-npm/registry.md b/deps/npm/docs/content/using-npm/registry.md index 3b07ab11c5b..4a265db03f0 100644 --- a/deps/npm/docs/content/using-npm/registry.md +++ b/deps/npm/docs/content/using-npm/registry.md @@ -30,6 +30,13 @@ The registry URL used is determined by the scope of the package (see supplied by the `registry` config parameter. See [`npm config`](/commands/npm-config), [`npmrc`](/configuring-npm/npmrc), and [`config`](/using-npm/config) for more on managing npm's configuration. +When the default registry is used in a package-lock or shrinkwrap is has the +special meaning of "the currently configured registry". If you create a lock +file while using the default registry you can switch to another registry and +npm will install packages from the new registry, but if you create a lock +file while using a custom registry packages will be installed from that +registry even after you change to another registry. + ### Does npm send any information about me back to the registry? Yes. diff --git a/deps/npm/docs/content/using-npm/scope.md b/deps/npm/docs/content/using-npm/scope.md index 62b4a685164..911d7ea5177 100644 --- a/deps/npm/docs/content/using-npm/scope.md +++ b/deps/npm/docs/content/using-npm/scope.md @@ -98,7 +98,8 @@ desired, with `npm access` or on the npmjs.com website. Scopes can be associated with a separate registry. This allows you to seamlessly use a mix of packages from the primary npm registry and one or more -private registries, such as npm Enterprise. +private registries, such as [GitHub Packages](https://github.com/features/packages) or the open source [Verdaccio](https://verdaccio.org) +project. You can associate a scope with a registry at login, e.g. diff --git a/deps/npm/docs/content/using-npm/workspaces.md b/deps/npm/docs/content/using-npm/workspaces.md index ae834c0cc7e..baf84f543f0 100644 --- a/deps/npm/docs/content/using-npm/workspaces.md +++ b/deps/npm/docs/content/using-npm/workspaces.md @@ -176,6 +176,22 @@ npm run test --workspaces Will run the `test` script in both `./packages/a` and `./packages/b`. +Commands will be run in each workspace in the order they appear in your `package.json` + +``` +{ + "workspaces": [ "packages/a", "packages/b" ] +} +``` + +Order of run is different with: + +``` +{ + "workspaces": [ "packages/b", "packages/a" ] +} +``` + ### Ignoring missing scripts It is not required for all of the workspaces to implement scripts run with the `npm run` command. diff --git a/deps/npm/docs/output/commands/npm-ls.html b/deps/npm/docs/output/commands/npm-ls.html index 0ce0ef1e18a..96b5405080b 100644 --- a/deps/npm/docs/output/commands/npm-ls.html +++ b/deps/npm/docs/output/commands/npm-ls.html @@ -159,7 +159,7 @@ tree at all, use <a href="../commands/npm-explain.html"><code>npm explain</code> 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@7.24.0 /path/to/npm +<pre lang="bash"><code>npm@8.0.0 /path/to/npm └─┬ init-package-json@0.0.4 └── promzard@0.1.5 </code></pre> diff --git a/deps/npm/docs/output/commands/npm.html b/deps/npm/docs/output/commands/npm.html index 0956b0ef0d9..9e948248988 100644 --- a/deps/npm/docs/output/commands/npm.html +++ b/deps/npm/docs/output/commands/npm.html @@ -148,7 +148,7 @@ npm command-line interface <pre lang="bash"><code>npm <command> [args] </code></pre> <h3 id="version">Version</h3> -<p>7.24.0</p> +<p>8.0.0</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 diff --git a/deps/npm/docs/output/configuring-npm/package-lock-json.html b/deps/npm/docs/output/configuring-npm/package-lock-json.html index 1e14f242bd6..41ee923047e 100644 --- a/deps/npm/docs/output/configuring-npm/package-lock-json.html +++ b/deps/npm/docs/output/configuring-npm/package-lock-json.html @@ -262,7 +262,8 @@ packages are listed with their relative paths from the root project folder.</p> the case of packages fetched from the registry, this will be a url to a tarball. In the case of git dependencies, this will be the full git url with commit sha. In the case of link dependencies, this will be the -location of the link target.</p> +location of the link target. <code>registry.npmjs.org</code> is a magic value meaning +“the currently configured registry”.</p> </li> <li> <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 @@ dependencies, this is the commit sha.</p> <li> <p>resolved: For registry sources this is path of the tarball relative to the registry URL. If the tarball URL isn’t on the same server as the -registry URL then this is a complete URL.</p> +registry URL then this is a complete URL. <code>registry.npmjs.org</code> is a magic +value meaning “the currently configured registry”.</p> </li> <li> <p>bundled: If true, this is the bundled dependency and will be installed diff --git a/deps/npm/docs/output/using-npm/registry.html b/deps/npm/docs/output/using-npm/registry.html index 3514ac72cd4..c32ca654c00 100644 --- a/deps/npm/docs/output/using-npm/registry.html +++ b/deps/npm/docs/output/using-npm/registry.html @@ -163,6 +163,12 @@ of which there is a public mirror at <a href="https://skimdb.npmjs.com/registry" <a href="../using-npm/scope.html"><code>scope</code></a>. If no scope is specified, the default registry is used, which is supplied by the <code>registry</code> config parameter. See <a href="../commands/npm-config.html"><code>npm config</code></a>, <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> +<p>When the default registry is used in a package-lock or shrinkwrap is has the +special meaning of “the currently configured registry”. If you create a lock +file while using the default registry you can switch to another registry and +npm will install packages from the new registry, but if you create a lock +file while using a custom registry packages will be installed from that +registry even after you change to another registry.</p> <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> <p>Yes.</p> <p>When making requests of the registry npm adds two headers with information diff --git a/deps/npm/docs/output/using-npm/scope.html b/deps/npm/docs/output/using-npm/scope.html index 630f3694ce4..922554b186d 100644 --- a/deps/npm/docs/output/using-npm/scope.html +++ b/deps/npm/docs/output/using-npm/scope.html @@ -206,7 +206,8 @@ desired, with <code>npm access</code> or on the npmjs.com website.</p> <h3 id="associating-a-scope-with-a-registry">Associating a scope with a registry</h3> <p>Scopes can be associated with a separate registry. This allows you to seamlessly use a mix of packages from the primary npm registry and one or more -private registries, such as npm Enterprise.</p> +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> +project.</p> <p>You can associate a scope with a registry at login, e.g.</p> <pre lang="bash"><code>npm login --registry=http://reg.example.com --scope=@myco </code></pre> diff --git a/deps/npm/docs/output/using-npm/workspaces.html b/deps/npm/docs/output/using-npm/workspaces.html index e4ce7a3840e..8efacb2260f 100644 --- a/deps/npm/docs/output/using-npm/workspaces.html +++ b/deps/npm/docs/output/using-npm/workspaces.html @@ -264,6 +264,16 @@ configured workspaces. e.g:</p> <pre><code>npm run test --workspaces </code></pre> <p>Will run the <code>test</code> script in both <code>./packages/a</code> and <code>./packages/b</code>.</p> +<p>Commands will be run in each workspace in the order they appear in your <code>package.json</code></p> +<pre><code>{ + "workspaces": [ "packages/a", "packages/b" ] +} +</code></pre> +<p>Order of run is different with:</p> +<pre><code>{ + "workspaces": [ "packages/b", "packages/a" ] +} +</code></pre> <h3 id="ignoring-missing-scripts">Ignoring missing scripts</h3> <p>It is not required for all of the workspaces to implement scripts run with the <code>npm run</code> command.</p> <p>By running the command with the <code>--if-present</code> flag, npm will ignore workspaces missing target script.</p> |