Table of Contents

About npm
- 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
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
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

Recovering your 2FA-enabled account

When you have two-factor access enabled on your account, and you lose the ability to provide the one-time password, you may be able to recover your account.

Misplaced second factor device

If you have misplaced the device that provided second-factor authentication, you can use the recovery codes generated when you enabled 2FA to access your account.

Locate the recovery codes generated when you enabled 2FA on your account.
If you are logged out, on the command line, log in using your npm username and npm password.
```
npm login
```
When prompted for an OTP, enter a recovery code.
Once you are logged in, type npm profile disable-2fa and enter your npm password if prompted.
Enter an unused recovery code when you see this prompt:
npm will confirm that two-factor authentication has been disabled.
type npm profile enable-2fa to re-enable 2FA, assign a different device to your account, and generate new recovery codes.

Note: Using the recovery codes to re-enable 2FA may create a second authenticator account with the same npm account name.

To delete the old authenticator account, follow the steps for the authenticator.

Misplaced recovery codes

If you have misplaced both the device that provided second-factor authentication and your recovery codes, we may be unable to help you recover your account. If you have any questions, please contact npm Support.

© npm, Inc. and Contributors
Licensed under the npm License.
npm is a trademark of npm, Inc.
https://docs.npmjs.com/recovering-your-2fa-enabled-account