Zoltan Kochan
07839df5c3
* docs: move website documentation into the pnpm repository * docs: keep v11 and v12 documentation beside their implementations * docs(pnpr): keep registry documentation beside its implementation * ci: classify product documentation as documentation changes * test: cover product documentation in Rust CI exclusions * ci: isolate documentation publishing and support manual sync * test: make dependency status fixture timestamps deterministic
1.3 KiB
id, title
| id | title |
|---|---|
| login | pnpm login |
Added in: v11.0.0
Aliases: adduser
Authenticate with an npm registry.
pnpm login [--registry <url>] [--scope <scope>]
Supports web-based login with QR code as well as classic username/password authentication.
Since v11.19.0, web-based login no longer requires an interactive terminal: without a TTY, pnpm login prints the authentication URL (skipping the QR code and the prompt to open the URL in a browser) and polls the registry until the browser approval completes. Only the classic username/password login still fails with ERR_PNPM_LOGIN_NON_INTERACTIVE in a non-interactive terminal.
Auth tokens are written to <pnpm config>/auth.ini.
Options
--registry <url>
The registry to authenticate with. Defaults to the configured default registry.
--scope <scope>
Associate the credentials with the specified scope. The registry for that scope will be used.
Since v11.25.0, a scope setting in a project's
pnpm-workspace.yaml is ignored with a warning. A repository must not be able
to choose the machine-wide route a later login writes. Pass --scope, set
PNPM_CONFIG_SCOPE, or set the machine's default with:
pnpm config set --global scope @acme