diff options
Diffstat (limited to 'deps/npm/html/doc/misc/npm-registry.html')
| -rw-r--r-- | deps/npm/html/doc/misc/npm-registry.html | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/deps/npm/html/doc/misc/npm-registry.html b/deps/npm/html/doc/misc/npm-registry.html index 16f8b7864c..ca2352a7ef 100644 --- a/deps/npm/html/doc/misc/npm-registry.html +++ b/deps/npm/html/doc/misc/npm-registry.html @@ -31,7 +31,7 @@ available at <a href="https://github.com/npm/npm-registry-couchapp">https://gith <code><a href="../misc/npm-scope.html">npm-scope(7)</a></code>). If no scope is specified, the default registry is used, which is supplied by the <code>registry</code> config parameter. See <code><a href="../cli/npm-config.html">npm-config(1)</a></code>, <code><a href="../files/npmrc.html">npmrc(5)</a></code>, and <code><a href="../misc/npm-config.html">npm-config(7)</a></code> for more on managing npm's configuration.</p> -<h2 id="does-npm-send-any-information-about-me-back-to-the-registry-">Does npm send any information about me back to the registry?</h2> +<h2 id="does-npm-send-any-information-about-me-back-to-the-registry">Does npm send any information about me back to the registry?</h2> <p>Yes.</p> <p>When making requests of the registry npm adds two headers with information about your environment:</p> @@ -51,7 +51,7 @@ build farms.</li> </ul> <p>The npm registry does not try to correlate the information in these headers with any authenticated accounts that may be used in the same requests.</p> -<h2 id="can-i-run-my-own-private-registry-">Can I run my own private registry?</h2> +<h2 id="can-i-run-my-own-private-registry">Can I run my own private registry?</h2> <p>Yes!</p> <p>The easiest way is to replicate the couch database, and use the same (or similar) design doc to implement the APIs.</p> @@ -61,20 +61,20 @@ to read any published packages, in addition to your private ones, and by default will only publish internally. </p> <p>If you then want to publish a package for the whole world to see, you can simply override the <code>--registry</code> option for that <code>publish</code> command.</p> -<h2 id="i-don-t-want-my-package-published-in-the-official-registry-it-s-private-">I don't want my package published in the official registry. It's private.</h2> +<h2 id="i-dont-want-my-package-published-in-the-official-registry-its-private">I don't want my package published in the official registry. It's private.</h2> <p>Set <code>"private": true</code> in your package.json to prevent it from being published at all, or <code>"publishConfig":{"registry":"http://my-internal-registry.local"}</code> to force it to be published only to your internal registry.</p> <p>See <code><a href="../files/package.json.html">package.json(5)</a></code> for more info on what goes in the package.json file.</p> -<h2 id="will-you-replicate-from-my-registry-into-the-public-one-">Will you replicate from my registry into the public one?</h2> +<h2 id="will-you-replicate-from-my-registry-into-the-public-one">Will you replicate from my registry into the public one?</h2> <p>No. If you want things to be public, then publish them into the public registry using npm. What little security there is would be for nought otherwise.</p> -<h2 id="do-i-have-to-use-couchdb-to-build-a-registry-that-npm-can-talk-to-">Do I have to use couchdb to build a registry that npm can talk to?</h2> +<h2 id="do-i-have-to-use-couchdb-to-build-a-registry-that-npm-can-talk-to">Do I have to use couchdb to build a registry that npm can talk to?</h2> <p>No, but it's way easier. Basically, yes, you do, or you have to effectively implement the entire CouchDB API anyway.</p> -<h2 id="is-there-a-website-or-something-to-see-package-docs-and-such-">Is there a website or something to see package docs and such?</h2> +<h2 id="is-there-a-website-or-something-to-see-package-docs-and-such">Is there a website or something to see package docs and such?</h2> <p>Yes, head over to <a href="https://www.npmjs.com/">https://www.npmjs.com/</a></p> <h2 id="see-also">SEE ALSO</h2> <ul> @@ -96,5 +96,5 @@ effectively implement the entire CouchDB API anyway.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-registry — npm@6.5.0</p> +<p id="footer">npm-registry — npm@6.7.0</p> |