About scopes

Note: You must be using npm version 2 or greater to use scopes. To upgrade to the latest version of npm, on the command line, run npm install [email protected] -g

When you sign up for an npm user account or create an Org, you are granted a scope that matches your user or Org name. You can use this scope as a namespace for related packages.

A scope allows you to create a package with the same name as a package created by another user or Org without conflict.

When listed as a dependent in a package.json file, scoped packages are preceded by their scope name. The scope name is everything between the @ and the slash:

To create and publish public scoped packages, see “Creating and publishing scoped public packages”.

To create and publish private scoped packages, see “Creating and publishing private packages”.

Scopes and package visibility

For more information on package scope and visibility, see “Package scope, access level, and visibility”.

< About packages and modules | About public packages >