UNPKG

npm

Version:

A package manager for node

npmjs.org/doc/

npm/npm

72 lines (46 loc) • 2.18 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
npm-adduser(1) -- Add a registry user account ============================================= ## SYNOPSIS npm adduser [--registry=url] [--scope=@orgname] [--always-auth] ## DESCRIPTION Create or verify a user named `<username>` in the specified registry, and save the credentials to the `.npmrc` file. If no registry is specified, the default registry will be used (see `npm-config(7)`). The username, password, and email are read in from prompts. To reset your password, go to <https://www.npmjs.org/forgot> To change your email address, go to <https://www.npmjs.org/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. `npm login` is an alias to `adduser` and behaves exactly the same way. ## CONFIGURATION ### registry Default: http://registry.npmjs.org/ The base URL of the npm package registry. If `scope` is also specified, this registry will only be used for packages with that scope. See `npm-scope(7)`. ### scope Default: none If specified, the user and login credentials given will be associated with the specified scope. See `npm-scope(7)`. You can use both at the same time, e.g. npm adduser --registry=http://myregistry.example.com --scope=@myco This will set a registry for the given scope and login or create a user for that registry at the same time. ### always-auth Default: false If specified, save configuration indicating that all requests to the given registry should include authorization information. Useful for private registries. Can be used with `--registry` and / or `--scope`, e.g. npm adduser --registry=http://private-registry.example.com --always-auth This will ensure that all requests to that registry (including for tarballs) include an authorization header. See `always-auth` in `npm-config(7)` for more details on always-auth. Registry-specific configuaration of `always-auth` takes precedence over any global configuration. ## SEE ALSO * npm-registry(7) * npm-config(1) * npm-config(7) * npmrc(5) * npm-owner(1) * npm-whoami(1)