FM / man1

/usr/local/lib/node_modules/npm/man/man1/

/usr/local/lib/node_modules/npm/man/man1

Name	Size	Mode	Actions
npm-access.1	3270	0644	edit dl rm
npm-adduser.1	2207	0644	edit dl rm
npm-audit.1	18066	0644	edit dl rm
npm-bugs.1	3390	0644	edit dl rm
npm-cache.1	3695	0644	edit dl rm
npm-ci.1	10884	0644	edit dl rm
npm-completion.1	999	0644	edit dl rm
npm-config.1	4646	0644	edit dl rm
npm-dedupe.1	10565	0644	edit dl rm
npm-deprecate.1	2379	0644	edit dl rm
npm-diff.1	9781	0644	edit dl rm
npm-dist-tag.1	5646	0644	edit dl rm
npm-docs.1	3372	0644	edit dl rm
npm-doctor.1	5374	0644	edit dl rm
npm-edit.1	1190	0644	edit dl rm
npm-exec.1	12510	0644	edit dl rm
npm-explain.1	2939	0644	edit dl rm
npm-explore.1	1091	0644	edit dl rm
npm-find-dupes.1	7586	0644	edit dl rm
npm-fund.1	4073	0644	edit dl rm
npm-get.1	546	0644	edit dl rm
npm-help-search.1	869	0644	edit dl rm
npm-help.1	1101	0644	edit dl rm
npm-init.1	11590	0644	edit dl rm
npm-install-ci-test.1	9023	0644	edit dl rm
npm-install-test.1	13086	0644	edit dl rm
npm-install.1	31718	0644	edit dl rm
npm-link.1	13653	0644	edit dl rm
npm-ll.1	6591	0644	edit dl rm
npm-login.1	2558	0644	edit dl rm
npm-logout.1	1889	0644	edit dl rm
npm-ls.1	7964	0644	edit dl rm
npm-org.1	2312	0644	edit dl rm
npm-outdated.1	7759	0644	edit dl rm
npm-owner.1	3365	0644	edit dl rm
npm-pack.1	4326	0644	edit dl rm
npm-ping.1	851	0644	edit dl rm
npm-pkg.1	8722	0644	edit dl rm
npm-prefix.1	1306	0644	edit dl rm
npm-profile.1	3423	0644	edit dl rm
npm-prune.1	6453	0644	edit dl rm
npm-publish.1	8842	0644	edit dl rm
npm-query.1	7688	0644	edit dl rm
npm-rebuild.1	5659	0644	edit dl rm
npm-repo.1	3154	0644	edit dl rm
npm-restart.1	1690	0644	edit dl rm
npm-root.1	1196	0644	edit dl rm
npm-run.1	8383	0644	edit dl rm
npm-sbom.1	8999	0644	edit dl rm
npm-search.1	4067	0644	edit dl rm
npm-set.1	1632	0644	edit dl rm
npm-shrinkwrap.1	999	0644	edit dl rm
npm-star.1	1809	0644	edit dl rm
npm-stars.1	797	0644	edit dl rm
npm-start.1	1824	0644	edit dl rm
npm-stop.1	1454	0644	edit dl rm
npm-team.1	4505	0644	edit dl rm
npm-test.1	1367	0644	edit dl rm
npm-token.1	5522	0644	edit dl rm
npm-trust.1	10532	0644	edit dl rm
npm-undeprecate.1	1579	0644	edit dl rm
npm-uninstall.1	4988	0644	edit dl rm
npm-unpublish.1	4902	0644	edit dl rm
npm-unstar.1	1660	0644	edit dl rm
npm-update.1	14461	0644	edit dl rm
npm-version.1	9064	0644	edit dl rm
npm-view.1	8076	0644	edit dl rm
npm-whoami.1	875	0644	edit dl rm
npm.1	5968	0644	edit dl rm
npx.1	6865	0644	edit dl rm

Edit: /usr/local/lib/node_modules/npm/man/man1/npm-team.1 (4505B)

.TH "NPM-TEAM" "1" "March 2026" "NPM@11.12.0" ""
.SH "NAME"
\fBnpm-team\fR - Manage organization teams and team memberships
.SS "Synopsis"
.P
.RS 2
.nf
npm team create <scope:team> \[lB]--otp <otpcode>\[rB]
npm team destroy <scope:team> \[lB]--otp <otpcode>\[rB]
npm team add <scope:team> <user> \[lB]--otp <otpcode>\[rB]
npm team rm <scope:team> <user> \[lB]--otp <otpcode>\[rB]
npm team ls <scope>|<scope:team>
.fi
.RE
.P
Note: This command is unaware of workspaces.
.SS "Description"
.P
Used to manage teams in organizations, and change team memberships. Does not handle permissions for packages.
.P
Teams must always be fully qualified with the organization/scope they belong to when operating on them, separated by a colon (\fB:\fR). That is, if you have a \fBnewteam\fR team in an \fBorg\fR organization, you must always refer to that team as \fB@org:newteam\fR in these commands.
.P
If you have two-factor authentication enabled in \fBauth-and-writes\fR mode, then you can provide a code from your authenticator with \fB\[lB]--otp <otpcode>\[rB]\fR. If you don't include this then you will be taken through a second factor flow based on your \fBauthtype\fR.
.RS 0
.IP \(bu 4
create / destroy: Create a new team, or destroy an existing one. Note: You cannot remove the \fBdevelopers\fR team, \fBlearn more.\fR \fI\(lahttps://docs.npmjs.com/about-developers-team\(ra\fR
.P
Here's how to create a new team \fBnewteam\fR under the \fBorg\fR org:
.P
.RS 2
.nf
npm team create @org:newteam
.fi
.RE
.P
You should see a confirming message such as: \fB+@org:newteam\fR once the new team has been created.
.IP \(bu 4
add: Add a user to an existing team.
.P
Adding a new user \fBusername\fR to a team named \fBnewteam\fR under the \fBorg\fR org:
.P
.RS 2
.nf
npm team add @org:newteam username
.fi
.RE
.P
On success, you should see a message: \fBusername added to @org:newteam\fR
.IP \(bu 4
rm: Using \fBnpm team rm\fR you can also remove users from a team they belong to.
.P
Here's an example removing user \fBusername\fR from \fBnewteam\fR team in \fBorg\fR organization:
.P
.RS 2
.nf
npm team rm @org:newteam username
.fi
.RE
.P
Once the user is removed a confirmation message is displayed: \fBusername removed from @org:newteam\fR
.IP \(bu 4
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.
.P
Here's an example of how to list all teams from an org named \fBorg\fR:
.P
.RS 2
.nf
npm team ls @org
.fi
.RE
.P
Example listing all members of a team named \fBnewteam\fR:
.P
.RS 2
.nf
npm team ls @org:newteam
.fi
.RE
.RE 0

.SS "Details"
.P
\fBnpm team\fR always operates directly on the current registry, configurable from the command line using \fB--registry=<registry url>\fR.
.P
You must be a \fIteam admin\fR 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.
.P
Organization creation and management of team admins and \fIorganization\fR members is done through the website, not the npm CLI.
.P
To use teams to manage permissions on packages belonging to your organization, use the \fBnpm access\fR command to grant or revoke the appropriate permissions.
.SS "Configuration"
.SS "\fBregistry\fR"
.RS 0
.IP \(bu 4
Default: "https://registry.npmjs.org/"
.IP \(bu 4
Type: URL
.RE 0

.P
The base URL of the npm registry.
.SS "\fBotp\fR"
.RS 0
.IP \(bu 4
Default: null
.IP \(bu 4
Type: null or String
.RE 0

.P
This is a one-time password from a two-factor authenticator. It's needed when publishing or changing package permissions with \fBnpm access\fR.
.P
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.
.SS "\fBparseable\fR"
.RS 0
.IP \(bu 4
Default: false
.IP \(bu 4
Type: Boolean
.RE 0

.P
Output parseable results from commands that write to standard output. For \fBnpm search\fR, this will be tab-separated table format.
.SS "\fBjson\fR"
.RS 0
.IP \(bu 4
Default: false
.IP \(bu 4
Type: Boolean
.RE 0

.P
Whether or not to output JSON data, rather than the normal output.
.RS 0
.IP \(bu 4
In \fBnpm pkg set\fR it enables parsing set values with JSON.parse() before saving them to your \fBpackage.json\fR.
.RE 0

.P
Not supported by all npm commands.
.SS "See Also"
.RS 0
.IP \(bu 4
npm help access
.IP \(bu 4
npm help config
.IP \(bu 4
npm help registry
.RE 0

cmd: