Movatterモバイル変換


[0]ホーム

URL:


Skip to searchSkip to content

Site navigation

npm-team

Manage organization teams and team memberships

Select CLI Version:

See DetailsTable of contents

Synopsis

npm team create<scope:team>[--otp<otpcode>]
npm team destroy<scope:team>[--otp<otpcode>]
npm teamadd<scope:team><user>[--otp<otpcode>]
npm teamrm<scope:team><user>[--otp<otpcode>]
npm teamls<scope>|<scope:team>

Note: This command is unaware of workspaces.

Description

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 anewteam team in anorg organization, you must always refer to that team as@org:newteam in these commands.

If you have two-factor authentication enabled inauth-and-writes mode, then you can provide a code from your authenticator with[--otp <otpcode>]. If you don't include this then you will be taken through a second factor flow based on yourauthtype.

  • create / destroy: Create a new team, or destroy an existing one. Note: You cannot remove thedevelopers team,learn more.

    Here's how to create a new teamnewteam under theorg org:

    npm team create @org:newteam

    You should see a confirming message such as:+@org:newteam once the new team has been created.

  • add: Add a user to an existing team.

    Adding a new userusername to a team namednewteam under theorg org:

    npm teamadd @org:newteam username

    On success, you should see a message:username added to @org:newteam

  • rm: Usingnpm team rm you can also remove users from a team they belong to.

    Here's an example removing userusername fromnewteam team inorg organization:

    npm teamrm @org:newteam username

    Once the user is removed a confirmation message is displayed:username removed from @org:newteam

  • ls: If performed on an organization name, will return a list of existing teams under that organization. If performed on a team, it will instead return a list of all users belonging to that particular team.

    Here's an example of how to list all teams from an org namedorg:

    npm teamls @org

    Example listing all members of a team namednewteam:

    npm teamls @org:newteam

Details

npm team always operates directly on the current registry, configurable from the command line using--registry=<registry url>.

You must be ateam admin to create teams and manage team membership, under the given organization. Listing teams and team memberships may be done by any member of the organization.

Organization creation and management of team admins andorganization members is done through the website, not the npm CLI.

To use teams to manage permissions on packages belonging to your organization, use thenpm access command to grant or revoke the appropriate permissions.

Configuration

registry

The base URL of the npm registry.

otp

  • Default: null
  • Type: null or String

This is a one-time password from a two-factor authenticator. It's needed when publishing or changing package permissions withnpm access.

If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one.

parseable

  • Default: false
  • Type: Boolean

Output parseable results from commands that write to standard output. Fornpm search, this will be tab-separated table format.

json

  • Default: false
  • Type: Boolean

Whether or not to output JSON data, rather than the normal output.

  • Innpm pkg set it enables parsing set values with JSON.parse() before saving them to yourpackage.json.

Not supported by all npm commands.

See Also

Edit this page on GitHub
3 contributorsjsoreflukekarrysMylesBorins
Last edited byjsoref onOctober 4, 2025

[8]ページ先頭

©2009-2025 Movatter.jp