/
home
/
techb158
/
.nvm
/
versions
/
node
/
v22.6.0
/
lib
/
node_modules
/
npm
/
man
/
man1
/
/home/techb158/.nvm/versions/node/v22.6.0/lib/node_modules/npm/man/man1
mkdir
upload
Name
Size
Mode
Actions
npm-access.1
4062
0644
edit
dl
rm
npm-adduser.1
1992
0644
edit
dl
rm
npm-audit.1
17381
0644
edit
dl
rm
npm-bugs.1
3379
0644
edit
dl
rm
npm-cache.1
3132
0644
edit
dl
rm
npm-ci.1
10181
0644
edit
dl
rm
npm-completion.1
997
0644
edit
dl
rm
npm-config.1
4636
0644
edit
dl
rm
npm-dedupe.1
9862
0644
edit
dl
rm
npm-deprecate.1
1892
0644
edit
dl
rm
npm-diff.1
9771
0644
edit
dl
rm
npm-dist-tag.1
5636
0644
edit
dl
rm
npm-docs.1
3361
0644
edit
dl
rm
npm-doctor.1
5372
0644
edit
dl
rm
npm-edit.1
1180
0644
edit
dl
rm
npm-exec.1
12491
0644
edit
dl
rm
npm-explain.1
2937
0644
edit
dl
rm
npm-explore.1
1089
0644
edit
dl
rm
npm-find-dupes.1
7590
0644
edit
dl
rm
npm-fund.1
4054
0644
edit
dl
rm
npm-help-search.1
867
0644
edit
dl
rm
npm-help.1
1099
0644
edit
dl
rm
npm-hook.1
2708
0644
edit
dl
rm
npm-init.1
11103
0644
edit
dl
rm
npm-install-ci-test.1
8320
0644
edit
dl
rm
npm-install-test.1
11149
0644
edit
dl
rm
npm-install.1
26964
0644
edit
dl
rm
npm-link.1
12950
0644
edit
dl
rm
npm-login.1
2345
0644
edit
dl
rm
npm-logout.1
1887
0644
edit
dl
rm
npm-ls.1
9419
0644
edit
dl
rm
npm-org.1
2310
0644
edit
dl
rm
npm-outdated.1
6377
0644
edit
dl
rm
npm-owner.1
3363
0644
edit
dl
rm
npm-pack.1
3876
0644
edit
dl
rm
npm-ping.1
849
0644
edit
dl
rm
npm-pkg.1
8704
0644
edit
dl
rm
npm-prefix.1
1317
0644
edit
dl
rm
npm-profile.1
3421
0644
edit
dl
rm
npm-prune.1
6457
0644
edit
dl
rm
npm-publish.1
8309
0644
edit
dl
rm
npm-query.1
7688
0644
edit
dl
rm
npm-rebuild.1
5664
0644
edit
dl
rm
npm-repo.1
3143
0644
edit
dl
rm
npm-restart.1
1709
0644
edit
dl
rm
npm-root.1
1194
0644
edit
dl
rm
npm-run-script.1
8377
0644
edit
dl
rm
npm-sbom.1
8996
0644
edit
dl
rm
npm-search.1
3952
0644
edit
dl
rm
npm-shrinkwrap.1
1004
0644
edit
dl
rm
npm-star.1
1807
0644
edit
dl
rm
npm-stars.1
795
0644
edit
dl
rm
npm-start.1
1835
0644
edit
dl
rm
npm-stop.1
1466
0644
edit
dl
rm
npm-team.1
4503
0644
edit
dl
rm
npm-test.1
1379
0644
edit
dl
rm
npm-token.1
3186
0644
edit
dl
rm
npm-uninstall.1
4986
0644
edit
dl
rm
npm-unpublish.1
4900
0644
edit
dl
rm
npm-unstar.1
1658
0644
edit
dl
rm
npm-update.1
13223
0644
edit
dl
rm
npm-version.1
7755
0644
edit
dl
rm
npm-view.1
6146
0644
edit
dl
rm
npm-whoami.1
873
0644
edit
dl
rm
npm.1
5947
0644
edit
dl
rm
npx.1
6407
0644
edit
dl
rm
Edit:
/home/techb158/.nvm/versions/node/v22.6.0/lib/node_modules/npm/man/man1/npm-team.1
(4503B)
.TH "NPM-TEAM" "1" "July 2024" "NPM@10.8.2" "" .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
Save
cmd:
run