Managing teams
© npm, Inc. and Contributors
Licensed under the npm License.
npm is a trademark of npm, Inc.
https://docs.npmjs.com/organizations/managing-teams
| Name | npm |
| Version | |
| Badge |
|
| Last Updated | 2022-01-11T05:35:52Z |
Table of Contents
- About npm
-
Config Settings
- _auth
- access
- all
- allow-same-version
- also
- audit
- audit-level
- auth-type
- before
- bin-links
- browser
- ca
- cache
- cache-max
- cache-min
- cafile
- call
- cert
- ci-name
- cidr
- color
- command-line-flags
- commit-hooks
- default-configs
- depth
- description
- dev
- diff
- diff-dst-prefix
- diff-ignore-all-space
- diff-name-only
- diff-no-prefix
- diff-src-prefix
- diff-text
- diff-unified
- dry-run
- editor
- engine-strict
- environment-variables
- fetch-retries
- fetch-retry-factor
- fetch-retry-maxtimeout
- fetch-retry-mintimeout
- fetch-timeout
- force
- foreground-scripts
- format-package-lock
- fund
- git
- git-tag-version
- global
- global-style
- globalconfig
- heading
- https-proxy
- if-present
- ignore-scripts
- include
- include-staged
- include-workspace-root
- init-author-email
- init-author-name
- init-author-url
- init-license
- init-module
- init-version
- initauthoremail
- initauthorname
- initauthorurl
- initlicense
- initmodule
- initversion
- json
- key
- legacy-bundling
- legacy-peer-deps
- link
- local-address
- location
- lockfile-version
- loglevel
- logs-max
- long
- maxsockets
- message
- node-options
- node-version
- noproxy
- npm-version
- npmrc-files
- offline
- omit
- only
- optional
- otp
- pack-destination
- package
- package-lock
- package-lock-only
- parseable
- prefer-offline
- prefer-online
- prefix
- preid
- production
- progress
- proxy
- read-only
- rebuild-bundle
- registry
- save
- save-bundle
- save-dev
- save-exact
- save-optional
- save-peer
- save-prefix
- save-prod
- scope
- script-shell
- searchexclude
- searchlimit
- searchopts
- searchstaleness
- shell
- shrinkwrap
- sign-git-commit
- sign-git-tag
- sso-poll-frequency
- sso-type
- strict-peer-deps
- strict-ssl
- tag
- tag-version-prefix
- timing
- tmp
- umask
- unicode
- update-notifier
- usage
- user-agent
- userconfig
- version
- versions
- viewer
- which
- workspace
- workspaces
- yes
-
Getting started
- About npm CLI versions
- About two-factor authentication
- Changing your npm username
- Common errors
- Configuring two-factor authentication
- Configuring your local environment
- Creating a new user account on the public registry
- Creating a strong password
- Deleting your npm user account
- Downgrading to a free user account plan
- Downloading and installing Node.js and npm
- Generating and locating npm-debug.log files
- Getting started
- Managing your npm user account
- Managing your profile settings
- Paying for your npm user account
- Receiving a one-time password over email
- Recovering your 2FA-enabled account
- Setting up your npm user account
- Troubleshooting
- Try the latest stable version of node
- Try the latest stable version of npm
- Updating user account billing settings
- Upgrading to a paid user account plan
- Viewing, downloading, and emailing receipts for your npm user account
- Integrations
-
npm CLI
- CLI commands
- CLI documentation
- config
- Configuring npm
- developers
- folders
- install
- Logging
- npm
- npm-access
- npm-adduser
- npm-audit
- npm-bin
- npm-bugs
- npm-cache
- npm-ci
- npm-completion
- npm-config
- npm-dedupe
- npm-deprecate
- npm-diff
- npm-dist-tag
- npm-docs
- npm-doctor
- npm-edit
- npm-exec
- npm-explain
- npm-explore
- npm-find-dupes
- npm-fund
- npm-help
- npm-help-search
- npm-hook
- npm-init
- npm-install
- npm-install-ci-test
- npm-install-test
- npm-link
- npm-logout
- npm-ls
- npm-org
- npm-outdated
- npm-owner
- npm-pack
- npm-ping
- npm-pkg
- npm-prefix
- npm-profile
- npm-prune
- npm-publish
- npm-rebuild
- npm-repo
- npm-restart
- npm-root
- npm-run-script
- npm-search
- npm-set-script
- npm-shrinkwrap
- npm-shrinkwrap.json
- npm-star
- npm-stars
- npm-start
- npm-stop
- npm-team
- npm-test
- npm-token
- npm-uninstall
- npm-unpublish
- npm-unstar
- npm-update
- npm-version
- npm-view
- npm-whoami
- npmrc
- npx
- orgs
- package-lock.json
- package.json
- registry
- removal
- scope
- scripts
- Using npm
- workspaces
-
Organizations
- About organization scopes and packages
- About the developers team
- Accepting or rejecting an organization invitation
- Adding members to your organization
- Adding organization members to teams
- Configuring your npm client with your organization settings
- Converting your user account to an organization
- Creating an organization
- Creating and managing organizations
- Creating and publishing an organization scoped package
- Creating teams
- Deleting an organization
- Downgrading to a free organization plan
- Managing organization members
- Managing organization packages
- Managing organization permissions
- Managing team access to organization packages
- Managing teams
- Organization roles and permissions
- Organizations
- Paying for your organization
- Removing members from your organization
- Removing organization members from teams
- Removing teams
- Renaming an organization
- Updating organization billing settings
- Upgrading to a paid organization plan
- Viewing, downloading, and emailing receipts for your organization
-
Package.json Settings
- bin
- browser
- bugs
- bundleddependencies
- config
- cpu
- default-values
- dependencies
- description
- devdependencies
- directories
- engines
- files
- funding
- homepage
- keywords
- license
- main
- man
- name
- optionaldependencies
- os
- overrides
- peerdependencies
- peerdependenciesmeta
- people-fields-author-contributors
- private
- publishconfig
- repository
- scripts
- see-also
- version
- workspaces
-
Packages and modules
- About audit reports
- About package PGP signatures
- About package README files
- About packages and modules
- About private packages
- About public packages
- About scopes
- About semantic versioning
- About the public npm registry
- Adding collaborators to private packages owned by a user account
- Adding dist-tags to packages
- Auditing package dependencies for security vulnerabilities
- Changing package visibility
- Contributing packages to the registry
- Creating a package.json file
- Creating and publishing private packages
- Creating and publishing scoped public packages
- Creating and publishing unscoped public packages
- Creating Node.js modules
- Deprecating and undeprecating packages or package versions
- Downloading and installing packages globally
- Downloading and installing packages locally
- Getting packages from the registry
- Introduction to packages and modules
- npm package scope, access level, and visibility
- Package name guidelines
- Packages and modules
- Reporting malware in an npm package
- Requiring 2FA for package publishing and settings modification
- Resolving EACCES permissions errors when installing packages globally
- Searching for and choosing packages to download
- Securing your code
- Specifying dependencies and devDependencies in a package.json file
- Transferring a package from a user account to another user account
- Uninstalling packages and dependencies
- Unpublishing packages from the registry
- Updating and managing your published packages
- Updating packages downloaded from the registry
- Updating your published package version number
- Using deprecated packages
- Using npm packages in your projects
- Verifying the PGP signature of a package from the npm public registry