@@ -7,7 +7,7 @@ description: Check the health of your npm environment
7
7
### Synopsis
8
8
9
9
``` bash
10
- npm doctor [ping ] [registry] [versions] [environment] [permissions] [cache]
10
+ npm doctor [connection ] [registry] [versions] [environment] [permissions] [cache]
11
11
```
12
12
13
13
Note: This command is unaware of workspaces.
@@ -38,20 +38,21 @@ there are any recommended changes, it will display them. By default npm
38
38
runs all of these checks. You can limit what checks are ran by
39
39
specifying them as extra arguments.
40
40
41
- #### ` npm ping `
41
+ #### ` Connecting to the registry `
42
42
43
43
By default, npm installs from the primary npm registry,
44
- ` registry.npmjs.org ` . ` npm doctor ` hits a special ping endpoint within the
45
- registry. This can also be checked with ` npm ping ` . If this check fails,
46
- you may be using a proxy that needs to be configured, or may need to talk
47
- to your IT staff to get access over HTTPS to ` registry.npmjs.org ` .
44
+ ` registry.npmjs.org ` . ` npm doctor ` hits a special connection testing
45
+ endpoint within the registry. This can also be checked with ` npm ping ` .
46
+ If this check fails, you may be using a proxy that needs to be
47
+ configured, or may need to talk to your IT staff to get access over
48
+ HTTPS to ` registry.npmjs.org ` .
48
49
49
50
This check is done against whichever registry you've configured (you can
50
51
see what that is by running ` npm config get registry ` ), and if you're using
51
52
a private registry that doesn't support the ` /whoami ` endpoint supported by
52
53
the primary registry, this check may fail.
53
54
54
- #### ` npm -v `
55
+ #### ` Checking npm version `
55
56
56
57
While Node.js may come bundled with a particular version of npm, it's the
57
58
policy of the CLI team that we recommend all users run ` npm@latest ` if they
@@ -61,7 +62,7 @@ support releases typically only receive critical security and regression
61
62
fixes. The team believes that the latest tested version of npm is almost
62
63
always likely to be the most functional and defect-free version of npm.
63
64
64
- #### ` node -v `
65
+ #### ` Checking node version `
65
66
66
67
For most users, in most circumstances, the best version of Node will be the
67
68
latest long-term support (LTS) release. Those of you who want access to new
@@ -70,7 +71,7 @@ be running a newer version, and some may be required to run an older
70
71
version of Node because of enterprise change control policies. That's OK!
71
72
But in general, the npm team recommends that most users run Node.js LTS.
72
73
73
- #### ` npm config get registry`
74
+ #### ` Checking configured npm registry`
74
75
75
76
You may be installing from private package registries for your project or
76
77
company. That's great! Others may be following tutorials or StackOverflow
@@ -79,7 +80,7 @@ Sometimes, this may entail changing the registry you're pointing at. This
79
80
part of ` npm doctor ` just lets you, and maybe whoever's helping you with
80
81
support, know that you're not using the default registry.
81
82
82
- #### ` which git`
83
+ #### ` Checking for git executable in PATH `
83
84
84
85
While it's documented in the README, it may not be obvious that npm needs
85
86
Git installed to do many of the things that it does. Also, in some cases
0 commit comments