Man page - npm-team(1)
Packages contains this manual
- npm-root(1)
- npm-explain(1)
- npm-whoami(1)
- npm-pack(1)
- npm-bugs(1)
- npm-view(1)
- npm-outdated(1)
- npm-update(1)
- npm-query(1)
- npm-logout(1)
- npm-deprecate(1)
- npm-exec(1)
- npm-ping(1)
- npm-shrinkwrap-json(5)
- npm-help(1)
- npm-prefix(1)
- npm-diff(1)
- npm-owner(1)
- npm-install(1)
- npmrc(5)
- npm-uninstall(1)
- npm-hook(1)
- npm-unstar(1)
- npm-docs(1)
- pacote(1)
- npm-restart(1)
- npm-star(1)
- npm-link(1)
- npm-test(1)
- npm-token(1)
- npm-arborist(1)
- npm-profile(1)
- npm-team(1)
- npx(1)
- npm-stars(1)
- npm-adduser(1)
- npm-cache(1)
- npm-edit(1)
- npm-doctor(1)
- npm-help-search(1)
- arborist(1)
- npm-rebuild(1)
- npm-repo(1)
- npm-publish(1)
- npm-start(1)
- npm-unpublish(1)
- npm-dedupe(1)
- npm-init(1)
- npm-dist-tag(1)
- npm-login(1)
- npm-config(1)
- npm(1)
- npm-search(1)
- npm-version(1)
- npm-org(1)
- npm-shrinkwrap(1)
- npm-ls(1)
- package-json(5)
- npm-stop(1)
- npm-install-test(1)
- npm-completion(1)
- npm-run-script(1)
- npm-prune(1)
- npm-access(1)
- npm-ci(1)
- npm-audit(1)
- npm-find-dupes(1)
- npm-install-ci-test(1)
- package-lock-json(5)
- npm-fund(1)
- npm-explore(1)
- npm-pkg(1)
- node-pacote
- node-npmcli-mock-registry
- node-npmcli-node-gyp
- node-libnpmorg
- npm
- node-libnpmteam
- node-npmcli-promise-spawn
- node-libnpmdiff
- node-npmcli-run-script
- node-npmcli-metavuln-calculator
- node-npmcli-smoke-tests
- node-libnpmpublish
- node-qrcode-terminal
- node-npmcli-config
- node-npmcli-git
- node-libnpmaccess
- node-npm-packlist
- node-npmcli-disparity-colors
- node-libnpmexec
- node-npmcli-installed-package-contents
- node-libnpmpack
- node-npmcli-map-workspaces
- node-npmcli-query
- node-npmcli-arborist
- node-npmcli-package-json
- node-libnpmhook
- node-npmcli-name-from-folder
- node-libnpmversion
- node-libnpmfund
- node-libnpmsearch
apt-get install npm
Manual
NPM-TEAM
NAMESynopsis
Description
Details
Configuration
See Also
NAME
npm-team
Synopsis
<!-- AUTOGENERATED USAGE DESCRIPTIONS -->
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 a
newteam
team in an
org
organization, you must
always refer to that team
as
@org:newteam
in these commands.
If you have
two-factor authentication enabled in
auth-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
prompted.
|
• |
create / destroy: |
Create a new team, or destroy
an existing one. Note: You cannot remove the
developers
team, <a
href="https://docs.npmjs.com/about-developers-team"
target="_blank">learn more.</a>
Here’s how to create a new team newteam under the org 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 user username to a team named newteam under the org org:
npm team add @org:newteam username
On success, you should see a message: username added to @org:newteam
|
• |
rm: |
Using npm team rm you can also remove users from a team they belong to.
Here’s an
example removing user
username
from
newteam
team
in
org
organization:
npm team rm @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 named org :
npm team ls @org
Example listing all members of a team named newteam :
npm team ls @org:newteam
Details
npm team
always operates directly on the current registry,
configurable from
the command line using
--registry=<registry
url>
.
You must be a
team 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 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.
Configuration
<!-- AUTOGENERATED CONFIG DESCRIPTIONS -->
See Also
|
• |
npm access |
|||
|
• |
npm config |
|||
|
• |
npm registry |