npm team create <scope:team>
npm team destroy <scope:team>
npm team add <scope:team> <user>
npm team rm <scope:team> <user>
npm team ls <scope>|<scope:team>
npm team edit <scope:team>
Used to manage teams in organizations, and change team memberships. Does not handle permissions for packages.
Teams must always be fully qualified with the organization/scope they belong to
when operating on them, separated by a colon (:
). That is, if you have a wombats
team in a wisdom
organization, you must always refer to that team as wisdom:wombats
in these commands.
developers
team, learn more.npm team
always operates directly on the current registry, configurable from
the command line using --registry=<registry url>
.
In order to create teams and manage team membership, you must be a team admin under the given organization. Listing teams and team memberships may be done by any member of the organizations.
Organization creation and management of team admins and organization members is done through the website, not the npm CLI.
To use teams to manage permissions on packages belonging to your organization,
use the npm access
command to grant or revoke the appropriate permissions.
👀 Found a typo? Let us know!
The current stable version of npm is here. To upgrade, run: npm install npm@latest -g
To report bugs or submit feature requests for the docs, please post here. Submit npm issues here.