FM / man1

/home/techb158/.nvm/versions/node/v16.20.2/lib/node_modules/npm/man/man1/

/home/techb158/.nvm/versions/node/v16.20.2/lib/node_modules/npm/man/man1

Name	Size	Mode	Actions
npm-access.1	3647	0644	edit dl rm
npm-adduser.1	2486	0644	edit dl rm
npm-audit.1	15987	0644	edit dl rm
npm-bin.1	957	0644	edit dl rm
npm-bugs.1	3300	0644	edit dl rm
npm-cache.1	3139	0644	edit dl rm
npm-ci.1	10760	0644	edit dl rm
npm-completion.1	1001	0644	edit dl rm
npm-config.1	4176	0644	edit dl rm
npm-dedupe.1	9181	0644	edit dl rm
npm-deprecate.1	1895	0644	edit dl rm
npm-diff.1	9867	0644	edit dl rm
npm-dist-tag.1	5532	0644	edit dl rm
npm-docs.1	3283	0644	edit dl rm
npm-doctor.1	5052	0644	edit dl rm
npm-edit.1	1140	0644	edit dl rm
npm-exec.1	12396	0644	edit dl rm
npm-explain.1	2963	0644	edit dl rm
npm-explore.1	1075	0644	edit dl rm
npm-find-dupes.1	6828	0644	edit dl rm
npm-fund.1	3992	0644	edit dl rm
npm-help-search.1	865	0644	edit dl rm
npm-help.1	1075	0644	edit dl rm
npm-hook.1	2691	0644	edit dl rm
npm-init.1	10165	0644	edit dl rm
npm-install-ci-test.1	8845	0644	edit dl rm
npm-install-test.1	8921	0644	edit dl rm
npm-install.1	24814	0644	edit dl rm
npm-link.1	12253	0644	edit dl rm
npm-logout.1	1895	0644	edit dl rm
npm-ls.1	9099	0644	edit dl rm
npm-org.1	2286	0644	edit dl rm
npm-outdated.1	6445	0644	edit dl rm
npm-owner.1	3392	0644	edit dl rm
npm-pack.1	3861	0644	edit dl rm
npm-ping.1	844	0644	edit dl rm
npm-pkg.1	8354	0644	edit dl rm
npm-prefix.1	1325	0644	edit dl rm
npm-profile.1	4707	0644	edit dl rm
npm-prune.1	6114	0644	edit dl rm
npm-publish.1	7937	0644	edit dl rm
npm-query.1	5480	0644	edit dl rm
npm-rebuild.1	4801	0644	edit dl rm
npm-repo.1	3075	0644	edit dl rm
npm-restart.1	1698	0644	edit dl rm
npm-root.1	1159	0644	edit dl rm
npm-run-script.1	8159	0644	edit dl rm
npm-search.1	3926	0644	edit dl rm
npm-set-script.1	2679	0644	edit dl rm
npm-shrinkwrap.1	977	0644	edit dl rm
npm-star.1	1793	0644	edit dl rm
npm-stars.1	776	0644	edit dl rm
npm-start.1	1827	0644	edit dl rm
npm-stop.1	1457	0644	edit dl rm
npm-team.1	4422	0644	edit dl rm
npm-test.1	1369	0644	edit dl rm
npm-token.1	5264	0644	edit dl rm
npm-uninstall.1	4534	0644	edit dl rm
npm-unpublish.1	4769	0644	edit dl rm
npm-unstar.1	1639	0644	edit dl rm
npm-update.1	12495	0644	edit dl rm
npm-version.1	7708	0644	edit dl rm
npm-view.1	5749	0644	edit dl rm
npm-whoami.1	866	0644	edit dl rm
npm.1	5804	0644	edit dl rm
npx.1	6313	0644	edit dl rm

Edit: /home/techb158/.nvm/versions/node/v16.20.2/lib/node_modules/npm/man/man1/npm-team.1 (4422B)

.TH "NPM\-TEAM" "1" "February 2023" "" ""
.SH "NAME"
\fBnpm-team\fR \- Manage organization teams and team memberships
.SS Synopsis
.P
.RS 2
.nf
npm team create <scope:team> [\-\-otp <otpcode>]
npm team destroy <scope:team> [\-\-otp <otpcode>]
npm team add <scope:team> <user> [\-\-otp <otpcode>]
npm team rm <scope:team> <user> [\-\-otp <otpcode>]
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:\fP)\. That is, if you have a
\fBnewteam\fP team in an \fBorg\fP organization, you must always refer to that team
as \fB@org:newteam\fP in these commands\.
.P
If you have two\-factor authentication enabled in \fBauth\-and\-writes\fP mode, then
you can provide a code from your authenticator with \fB[\-\-otp <otpcode>]\fP\|\.
If you don't include this then you will be prompted\.
.RS 0
.IP \(bu 2
create / destroy:
Create a new team, or destroy an existing one\. Note: You cannot remove the
\fBdevelopers\fP team, <a href="https://docs\.npmjs\.com/about\-developers\-team" target="_blank">learn more\.</a>
Here's how to create a new team \fBnewteam\fP under the \fBorg\fP org:
.P
.RS 2
.nf
npm team create @org:newteam
.fi
.RE
You should see a confirming message such as: \fB+@org:newteam\fP once the new
team has been created\.
.IP \(bu 2
add:
Add a user to an existing team\.
Adding a new user \fBusername\fP to a team named \fBnewteam\fP under the \fBorg\fP org:
.P
.RS 2
.nf
npm team add @org:newteam username
.fi
.RE
On success, you should see a message: \fBusername added to @org:newteam\fP
.IP \(bu 2
rm:
Using \fBnpm team rm\fP you can also remove users from a team they belong to\.
Here's an example removing user \fBusername\fP from \fBnewteam\fP team
in \fBorg\fP organization:
.P
.RS 2
.nf
npm team rm @org:newteam username
.fi
.RE
Once the user is removed a confirmation message is displayed:
\fBusername removed from @org:newteam\fP
.IP \(bu 2
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 \fBorg\fP:
.P
.RS 2
.nf
npm team ls @org
.fi
.RE
Example listing all members of a team named \fBnewteam\fP:
.P
.RS 2
.nf
npm team ls @org:newteam
.fi
.RE

.RE
.SS Details
.P
\fBnpm team\fP always operates directly on the current registry, configurable from
the command line using \fB\-\-registry=<registry url>\fP\|\.
.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\fP command to grant or revoke the appropriate permissions\.
.SS Configuration
.SS \fBregistry\fP
.RS 0
.IP \(bu 2
Default: "https://registry\.npmjs\.org/"
.IP \(bu 2
Type: URL

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

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

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

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

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

.RE

cmd: