diff options
Diffstat (limited to 'deps/npm/docs/output/using-npm')
| -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 |
3 files changed, 18 insertions, 1 deletions
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> |