diff options
author | Kat Marchán <kzm@sykosomatic.org> | 2015-07-24 15:09:52 -0700 |
---|---|---|
committer | Jeremiah Senkpiel <fishrock123@rocketmail.com> | 2015-07-24 18:19:40 -0700 |
commit | b73a7465c5b5aadaeb64de9ff4e56a06e98ab336 (patch) | |
tree | 68aa5634729c6ec18379bfe1020d40299d228dc1 /deps/npm/man/man7/npm-registry.7 | |
parent | 68b06e94e3e1de11c45b613aff9836310360a8e2 (diff) | |
download | android-node-v8-b73a7465c5b5aadaeb64de9ff4e56a06e98ab336.tar.gz android-node-v8-b73a7465c5b5aadaeb64de9ff4e56a06e98ab336.tar.bz2 android-node-v8-b73a7465c5b5aadaeb64de9ff4e56a06e98ab336.zip |
deps: upgrade to npm 2.13.2
PR-URL: https://github.com/nodejs/io.js/pull/2241
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Diffstat (limited to 'deps/npm/man/man7/npm-registry.7')
-rw-r--r-- | deps/npm/man/man7/npm-registry.7 | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/deps/npm/man/man7/npm-registry.7 b/deps/npm/man/man7/npm-registry.7 index 9f4914e9a0..a1cf07f1d8 100644 --- a/deps/npm/man/man7/npm-registry.7 +++ b/deps/npm/man/man7/npm-registry.7 @@ -17,9 +17,9 @@ http://skimdb\.npmjs\.com/registry\|\. The code for the couchapp is available at http://github\.com/npm/npm\-registry\-couchapp\|\. .P The registry URL used is determined by the scope of the package (see -npm help 7 \fBnpm\-scope\fR)\. If no scope is specified, the default registry is used, which is -supplied by the \fBregistry\fR config parameter\. See npm help \fBnpm\-config\fR, -npm help 5 \fBnpmrc\fR, and npm help 7 \fBnpm\-config\fR for more on managing npm's configuration\. +npm help 7 \fBnpm\-scope\fP)\. If no scope is specified, the default registry is used, which is +supplied by the \fBregistry\fP config parameter\. See npm help \fBnpm\-config\fP, +npm help 5 \fBnpmrc\fP, and npm help 7 \fBnpm\-config\fP for more on managing npm's configuration\. .SH Can I run my own private registry? .P Yes! @@ -33,15 +33,15 @@ to read any published packages, in addition to your private ones, and by default will only publish internally\. .P If you then want to publish a package for the whole world to see, you can -simply override the \fB\-\-registry\fR option for that \fBpublish\fR command\. +simply override the \fB\-\-registry\fP option for that \fBpublish\fP command\. .SH I don't want my package published in the official registry\. It's private\. .P -Set \fB"private": true\fR in your package\.json to prevent it from being +Set \fB"private": true\fP in your package\.json to prevent it from being published at all, or -\fB"publishConfig":{"registry":"http://my\-internal\-registry\.local"}\fR +\fB"publishConfig":{"registry":"http://my\-internal\-registry\.local"}\fP to force it to be published only to your internal registry\. .P -See npm help 5 \fBpackage\.json\fR for more info on what goes in the package\.json file\. +See npm help 5 \fBpackage\.json\fP for more info on what goes in the package\.json file\. .SH Will you replicate from my registry into the public one? .P No\. If you want things to be public, then publish them into the public |