/var/lang/lib/node_modules/npm/docs/content/commands
This explorer reads the filesystem of the server it runs on, so /workspace/user isn't present here. Browsing and the terminal still work against this server's own disk from /.
---title: npm-loginsection: 1description: Login to a registry user account--- ### Synopsis ```bashnpm login``` Note: This command is unaware of workspaces. ### Description Verify a user in the specified registry, and save the credentials to the`.npmrc` file.If no registry is specified, the default registry will be used (see [`config`](/using-npm/config)). When you run `npm login`, the CLI automatically generates a legacy token of `publish` type.For more information, see [About legacy tokens](/about-access-tokens#about-legacy-tokens). When using `legacy` for your `auth-type`, the username and password, are read in from prompts. To reset your password, go to <https://www.npmjs.com/forgot> To change your email address, go to <https://www.npmjs.com/email-edit> You may use this command multiple times with the same user account to authorize on a new machine.When authenticating on a new machine, the username, password and email address must all match with your existing record. ### Configuration #### `registry` * Default: "https://registry.npmjs.org/"* Type: URL The base URL of the npm registry. #### `scope` * Default: the scope of the current project, if any, or ""* Type: String Associate an operation with a scope for a scoped registry. Useful when logging in to or out of a private registry: ```# log in, linking the scope to the custom registrynpm login --scope=@mycorp --registry=https://registry.mycorp.com # log out, removing the link and the auth tokennpm logout --scope=@mycorp``` This will cause `@mycorp` to be mapped to the registry for futureinstallation of packages specified according to the pattern`@mycorp/package`. This will also cause `npm init` to create a scoped package. ```# accept all defaults, and create a package named "@foo/whatever",# instead of just named "whatever"npm init --scope=@foo --yes``` #### `auth-type` * Default: "web"* Type: "legacy" or "web" What authentication strategy to use with `login`. Note that if an `otp`config is given, this value will always be set to `legacy`. ### See Also * [npm registry](/using-npm/registry)* [npm config](/commands/npm-config)* [npmrc](/configuring-npm/npmrc)* [npm owner](/commands/npm-owner)* [npm whoami](/commands/npm-whoami)* [npm token](/commands/npm-token)* [npm profile](/commands/npm-profile)