diff options
Diffstat (limited to 'deps/npm/man/man7/npm-scope.7')
| -rw-r--r-- | deps/npm/man/man7/npm-scope.7 | 32 |
1 files changed, 16 insertions, 16 deletions
diff --git a/deps/npm/man/man7/npm-scope.7 b/deps/npm/man/man7/npm-scope.7 index 29586c7a7..4bfe58c7f 100644 --- a/deps/npm/man/man7/npm-scope.7 +++ b/deps/npm/man/man7/npm-scope.7 @@ -1,4 +1,4 @@ -.TH "NPM\-SCOPE" "7" "June 2015" "" "" +.TH "NPM\-SCOPE" "7" "August 2015" "" "" .SH "NAME" \fBnpm-scope\fR \- Scoped packages .SH DESCRIPTION @@ -23,13 +23,13 @@ used to work with scoped and un\-scoped registries at the same time\. .SH Installing scoped packages .P Scoped packages are installed to a sub\-folder of the regular installation -folder, e\.g\. if your other packages are installed in \fBnode_modules/packagename\fR, -scoped modules will be in \fBnode_modules/@myorg/packagename\fR\|\. The scope folder -(\fB@myorg\fR) is simply the name of the scope preceded by an @\-symbol, and can +folder, e\.g\. if your other packages are installed in \fBnode_modules/packagename\fP, +scoped modules will be in \fBnode_modules/@myorg/packagename\fP\|\. The scope folder +(\fB@myorg\fP) is simply the name of the scope preceded by an @\-symbol, and can contain any number of scoped packages\. .P A scoped package is installed by referencing it by name, preceded by an -@\-symbol, in \fBnpm install\fR: +@\-symbol, in \fBnpm install\fP: .P .RS 2 .nf @@ -37,7 +37,7 @@ npm install @myorg/mypackage .fi .RE .P -Or in \fBpackage\.json\fR: +Or in \fBpackage\.json\fP: .P .RS 2 .nf @@ -48,7 +48,7 @@ Or in \fBpackage\.json\fR: .RE .P Note that if the @\-symbol is omitted in either case npm will instead attempt to -install from GitHub; see npm help \fBnpm\-install\fR\|\. +install from GitHub; see npm help \fBnpm\-install\fP\|\. .SH Requiring scoped packages .P Because scoped packages are installed into a scope folder, you have to @@ -61,7 +61,7 @@ require('@myorg/mypackage') .RE .P There is nothing special about the way Node treats scope folders, this is -just specifying to require the module \fBmypackage\fR in the folder called \fB@myorg\fR\|\. +just specifying to require the module \fBmypackage\fP in the folder called \fB@myorg\fP\|\. .SH Publishing scoped packages .P Scoped packages can be published to any registry that supports them, including @@ -72,19 +72,19 @@ the public npm registry\. If you wish, you may associate a scope with a registry; see below\. .SS Publishing public scoped packages to the public npm registry .P -To publish a public scoped package, you must specify \fB\-\-access public\fR with +To publish a public scoped package, you must specify \fB\-\-access public\fP with the initial publication\. This will publish the package and set access -to \fBpublic\fR as if you had run \fBnpm access public\fR after publishing\. +to \fBpublic\fP as if you had run \fBnpm access public\fP after publishing\. .SS Publishing private scoped packages to the npm registry .P To publish a private scoped package to the npm registry, you must have an npm Private Modules \fIhttps://www\.npmjs\.com/private\-modules\fR account\. .P -You can then publish the module with \fBnpm publish\fR or \fBnpm publish -\-\-access restricted\fR, and it will be present in the npm registry, with +You can then publish the module with \fBnpm publish\fP or \fBnpm publish +\-\-access restricted\fP, and it will be present in the npm registry, with restricted access\. You can then change the access permissions, if -desired, with \fBnpm access\fR or on the npmjs\.com website\. +desired, with \fBnpm access\fP or on the npmjs\.com website\. .SH Associating a scope with a registry .P Scopes can be associated with a separate registry\. This allows you to @@ -102,7 +102,7 @@ npm login \-\-registry=http://reg\.example\.com \-\-scope=@myco Scopes have a many\-to\-one relationship with registries: one registry can host multiple scopes, but a scope only ever points to one registry\. .P -You can also associate a scope with a registry using \fBnpm config\fR: +You can also associate a scope with a registry using \fBnpm config\fP: .P .RS 2 .nf @@ -110,9 +110,9 @@ npm config set @myco:registry http://reg\.example\.com .fi .RE .P -Once a scope is associated with a registry, any \fBnpm install\fR for a package +Once a scope is associated with a registry, any \fBnpm install\fP for a package with that scope will request packages from that registry instead\. Any -\fBnpm publish\fR for a package name that contains the scope will be published to +\fBnpm publish\fP for a package name that contains the scope will be published to that registry instead\. .SH SEE ALSO .RS 0 |