diff options
Diffstat (limited to 'deps/npm/man/man1/npm-adduser.1')
| -rw-r--r-- | deps/npm/man/man1/npm-adduser.1 | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/deps/npm/man/man1/npm-adduser.1 b/deps/npm/man/man1/npm-adduser.1 index 4c8015eff..ca4155402 100644 --- a/deps/npm/man/man1/npm-adduser.1 +++ b/deps/npm/man/man1/npm-adduser.1 @@ -1,4 +1,4 @@ -.TH "NPM\-ADDUSER" "1" "June 2015" "" "" +.TH "NPM\-ADDUSER" "1" "August 2015" "" "" .SH "NAME" \fBnpm-adduser\fR \- Add a registry user account .SH SYNOPSIS @@ -10,9 +10,9 @@ npm adduser [\-\-registry=url] [\-\-scope=@orgname] [\-\-always\-auth] .RE .SH DESCRIPTION .P -Create or verify a user named \fB<username>\fR in the specified registry, and -save the credentials to the \fB\|\.npmrc\fR file\. If no registry is specified, -the default registry will be used (see npm help 7 \fBnpm\-config\fR)\. +Create or verify a user named \fB<username>\fP in the specified registry, and +save the credentials to the \fB\|\.npmrc\fP file\. If no registry is specified, +the default registry will be used (see npm help 7 \fBnpm\-config\fP)\. .P The username, password, and email are read in from prompts\. .P @@ -25,20 +25,20 @@ authorize on a new machine\. When authenticating on a new machine, the username, password and email address must all match with your existing record\. .P -\fBnpm login\fR is an alias to \fBadduser\fR and behaves exactly the same way\. +\fBnpm login\fP is an alias to \fBadduser\fP and behaves exactly the same way\. .SH CONFIGURATION .SS registry .P Default: http://registry\.npmjs\.org/ .P -The base URL of the npm package registry\. If \fBscope\fR is also specified, -this registry will only be used for packages with that scope\. See npm help 7 \fBnpm\-scope\fR\|\. +The base URL of the npm package registry\. If \fBscope\fP is also specified, +this registry will only be used for packages with that scope\. See npm help 7 \fBnpm\-scope\fP\|\. .SS scope .P Default: none .P If specified, the user and login credentials given will be associated -with the specified scope\. See npm help 7 \fBnpm\-scope\fR\|\. You can use both at the same time, +with the specified scope\. See npm help 7 \fBnpm\-scope\fP\|\. You can use both at the same time, e\.g\. .P .RS 2 @@ -55,7 +55,7 @@ Default: false .P If specified, save configuration indicating that all requests to the given registry should include authorization information\. Useful for private -registries\. Can be used with \fB\-\-registry\fR and / or \fB\-\-scope\fR, e\.g\. +registries\. Can be used with \fB\-\-registry\fP and / or \fB\-\-scope\fP, e\.g\. .P .RS 2 .nf @@ -64,8 +64,8 @@ npm adduser \-\-registry=http://private\-registry\.example\.com \-\-always\-auth .RE .P This will ensure that all requests to that registry (including for tarballs) -include an authorization header\. See \fBalways\-auth\fR in npm help 7 \fBnpm\-config\fR for more -details on always\-auth\. Registry\-specific configuration of \fBalways\-auth\fR takes +include an authorization header\. See \fBalways\-auth\fP in npm help 7 \fBnpm\-config\fP for more +details on always\-auth\. Registry\-specific configuration of \fBalways\-auth\fP takes precedence over any global configuration\. .SH SEE ALSO .RS 0 |