diff options
| author | Henry Zhu <hi@henryzoo.com> | 2017-01-25 17:15:23 +0300 |
|---|---|---|
| committer | Kat Marchán <kzm@sykosomatic.org> | 2017-01-25 17:15:23 +0300 |
| commit | af06aa9a357578a8fd58c575f3dbe55bc65fc376 (patch) | |
| tree | b4ec9e3cfff9e68e300d284917deb13447162ee4 /doc | |
| parent | 2ee45a884137ae0706b7c741c671fef2cb3bac96 (diff) | |
doc: add section about scopes only belonging to user/org (#15520)
PR-URL: https://github.com/npm/npm/pull/15520
Fixes: https://github.com/npm/docs/issues/795
Credit: @hzoo
Reviewed-By: @iarna
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/misc/npm-scope.md | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/misc/npm-scope.md b/doc/misc/npm-scope.md index 98e7bc58e..940c1dbb5 100644 --- a/doc/misc/npm-scope.md +++ b/doc/misc/npm-scope.md @@ -13,6 +13,11 @@ and followed by a slash, e.g. Scopes are a way of grouping related packages together, and also affect a few things about the way npm treats the package. +Each npm user/organization has their own scope, and only you can add packages +in your scope. This means you don't have to worry about someone taking your +package name ahead of you. Thus it is also a good way to signal official packages +for organizations. + Scoped packages can be published and installed as of `npm@2` and are supported by the primary npm registry. Unscoped packages can depend on scoped packages and vice versa. The npm client is backwards-compatible with unscoped registries, |