Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit 1fae98b

Browse filesBrowse files
iarnaItalo A. Casas
iarna
authored and
Italo A. Casas
committed
deps: upgrade npm to 4.1.1
PR-URL: #10781 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
1 parent fa8baa2 commit 1fae98b
Copy full SHA for 1fae98b

File tree

Expand file treeCollapse file tree

347 files changed

+4716
-6785
lines changed
Open diff view settings
Filter options

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
Dismiss banner
Expand file treeCollapse file tree

347 files changed

+4716
-6785
lines changed
Open diff view settings
Collapse file

‎deps/npm/AUTHORS‎

Copy file name to clipboardExpand all lines: deps/npm/AUTHORS
+1Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -445,3 +445,4 @@ Alex Jordan <alex@strugee.net>
445445
Ville Lahdenvuo <tuhoojabotti@gmail.com>
446446
Natalie Wolfe <nwolfe@newrelic.com>
447447
Andrew Schmadel <aschmadel@learningobjects.com>
448+
Jonah Moses <jonahkmoses@gmail.com>
Collapse file

‎deps/npm/CHANGELOG.md‎

Copy file name to clipboardExpand all lines: deps/npm/CHANGELOG.md
+217-3Lines changed: 217 additions & 3 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,216 @@
1+
### v4.1.1 (2016-12-16)
2+
3+
This fixes a bug in the metrics reporting where, if you had enabled it then
4+
installs would create a metrics reporting process, that would create a
5+
metrics reporting process, that would… well, you get the idea. The only
6+
way to actually kill these processes is to turn off your networking, then
7+
on MacOS/Linux kill them with `kill -9`. Alternatively you can just reboot.
8+
9+
Anyway, this is a quick release to fix that bug:
10+
11+
* [`51c393f`](https://github.com/npm/npm/commit/51c393feff5f4908c8a9fb02baef505b1f2259be)
12+
[#15237](https://github.com/npm/npm/pull/15237)
13+
Don't launch a metrics sender process if we're runnning from a metrics
14+
sender process.
15+
([@iarna](https://github.com/iarna))
16+
17+
### v4.1.0 (2016-12-15)
18+
19+
I'm really excited about `npm@4.1.0`. I know, I know, I'm kinda overexcited
20+
in my changelogs, but this one is GREAT. We've got a WHOLE NEW subcommand, I
21+
mean, when was the last time you saw that? YEARS! And we have the beginnings
22+
of usage metrics reporting. Then there's a fix for a really subtle bug that
23+
resulted in `shasum` errors. And then we also have a few more bug fixes and
24+
other improvements.
25+
26+
#### ANONYMOUS METRIC REPORTING
27+
28+
We're adding the ability for you all to help us track the quality of your
29+
experiences using `npm`. Metrics will be sent if you run:
30+
31+
```
32+
npm config set send-metrics true
33+
```
34+
35+
Then `npm` will report to `registry.npmjs.org` the number of successful and
36+
failed installations you've had. The data contains no identifying
37+
information and npm will not attempt to correlate things like IP address
38+
with the metrics being submitted.
39+
40+
Currently we only track number of successful and failed installations. In
41+
the future we would like to find additional metrics to help us better
42+
quantify the quality of the `npm` experience.
43+
44+
* [`190a658`](https://github.com/npm/npm/commit/190a658c4222f6aa904cbc640fc394a5c875e4db)
45+
[#15084](https://github.com/npm/npm/pull/15084)
46+
Add facility for recording and reporting success metrics.
47+
([@iarna](https://github.com/iarna))
48+
* [`87afc8b`](https://github.com/npm/npm/commit/87afc8b466f553fb49746c932c259173de48d0a4)
49+
[npm/npm-registry-client#147](https://github.com/npm/npm-registry-client/pull/148)
50+
`npm-registry-client@7.4.5`:
51+
Add support for sending anonymous CLI metrics.
52+
([@iarna](https://github.com/iarna),
53+
[@sisidovski](https://github.com/sisidovski))
54+
55+
### NPM DOCTOR
56+
57+
<pre>
58+
<u>Check</u> <u>Value</u> <u>Recommendation</u>
59+
npm ping ok
60+
npm -v v4.0.5
61+
node -v v4.6.1 Use node v6.9.2
62+
npm config get registry https://registry.npmjs.org/
63+
which git /Users/rebecca/bin/git
64+
Perms check on cached files ok
65+
Perms check on global node_modules ok
66+
Perms check on local node_modules ok
67+
Checksum cached files ok
68+
</pre>
69+
70+
It's a rare day that we add a new command to `npm`, so I'm excited to
71+
present to you `npm doctor`. It checks for a number of common problems and
72+
provides some recommended solutions. It was put together through the hard
73+
work of [@watilde](https://github.com/watilde).
74+
75+
* [`2359505`](https://github.com/npm/npm/commit/23595055669f76c9fe8f5f1cf4a705c2e794f0dc)
76+
[`0209ee5`](https://github.com/npm/npm/commit/0209ee50448441695fbf9699019d34178b69ba73)
77+
[#14582](https://github.com/npm/npm/pull/14582)
78+
Add new `npm doctor` to give your project environment a health check.
79+
([@watilde](https://github.com/watilde))
80+
81+
#### FIX MAJOR SOURCE OF SHASUM ERRORS
82+
83+
If you've been getting intermittent shasum errors then you'll be pleased to
84+
know that we've tracked down at least one source of them, if not THE source
85+
of them.
86+
87+
* [`87afc8b`](https://github.com/npm/npm/commit/87afc8b466f553fb49746c932c259173de48d0a4)
88+
[#14626](https://github.com/npm/npm/issues/14626)
89+
[npm/npm-registry-client#148](https://github.com/npm/npm-registry-client/pull/148)
90+
`npm-registry-client@7.4.5`:
91+
Fix a bug where an `ECONNRESET` while fetching a package file would result
92+
in a partial download that would be reported as a "shasum mismatch". It
93+
now throws away the partial download and retries it.
94+
([@iarna](https://github.com/iarna))
95+
96+
#### FILE URLS AND NODE.JS 7
97+
98+
When `npm` was formatting `file` URLs we took advantage of `url.format` to
99+
construct them. Node.js 7 changed the behavior in such a way that our use of
100+
`url.format` stopped producing URLs that we could make use of.
101+
102+
The reasons for this have to do with the `file` URL specification and how
103+
invalid (according to the specification) URLs are handled. How this changed
104+
is most easily explained with a table:
105+
106+
<table>
107+
<tr><th></th><th>URL</th><th>Node.js &lt;= 6</th><th><tt>npm</tt>'s understanding</th><th>Node.js 7</th><th><tt>npm</tt>'s understanding</th></tr>
108+
<tr><td>VALID</td><td><tt>file:///abc/def</tt></td><td><tt>file:///abc/def</tt></td><td><tt>/abc/def</tt></td><td><tt>file:///abc/def</tt></td><td><tt>/abc/def</tt></td></tr>
109+
<tr><td>invalid</td><td><tt>file:/abc/def</tt></td><td><tt>file:/abc/def</tt></td><td><tt>/abc/def</tt></td><td><tt>file:///abc/def</tt></td><td><tt>/abc/def</tt></td></tr>
110+
<tr><td>invalid</td><td><tt>file:abc/def</tt></td><td><tt>file:abc/def</tt></td><td><tt>$CWD/abc/def</tt></td><td><tt>file://abc/def</tt></td><td><tt>/def</tt> on the <tt>abc</tt> host</td></tr>
111+
<tr><td>invalid</td><td><tt>file:../abc/def</tt></td><td><tt>file:../abc/def</tt></td><td><tt>$CWD/../abc/def</tt></td><td><tt>file://../abc/def</tt></td><td><tt>/abc/def</tt> on the <tt>..</tt> host</td></tr>
112+
</table>
113+
114+
So the result was that passing a `file` URL that npm had received that used
115+
through Node.js 7's `url.format` changed its meaning as far as `npm` was
116+
concerned. As those kinds of URLs are, per the specification, invalid, how
117+
they should be handled is undefined and so the change in Node.js wasn't a
118+
bug per se.
119+
120+
Our solution is to stop using `url.format` when constructing this kind of
121+
URL.
122+
123+
* [`173935b`](https://github.com/npm/npm/commit/173935b4298e09c4fdcb8f3a44b06134d5aff181)
124+
[#15114](https://github.com/npm/npm/issues/15114)
125+
Stop using `url.format` for relative local dep paths.
126+
([@zkat](https://github.com/zkat))
127+
128+
#### EXTRANEOUS LIFECYCLE SCRIPT EXECUTION WHEN REMOVING
129+
130+
* [`afb1dfd`](https://github.com/npm/npm/commit/afb1dfd944e57add25a05770c0d52d983dc4e96c)
131+
[#15090](https://github.com/npm/npm/pull/15090)
132+
Skip top level lifecycles when uninstalling.
133+
([@iarna](https://github.com/iarna))
134+
135+
#### REFACTORING AND INTERNALS
136+
137+
* [`c9b279a`](https://github.com/npm/npm/commit/c9b279aca0fcb8d0e483e534c7f9a7250e2a9392)
138+
[#15205](https://github.com/npm/npm/pull/15205)
139+
[#15196](https://github.com/npm/npm/pull/15196)
140+
Only have one function that determines which version of a package to use
141+
given a specifier and a list of versions.
142+
([@iarna](https://github.com/iarna),
143+
[@zkat](https://github.com/zkat))
144+
145+
* [`981ce63`](https://github.com/npm/npm/commit/981ce6395e7892dde2591b44e484e191f8625431)
146+
[#15090](https://github.com/npm/npm/pull/15090)
147+
Rewrite prune to use modern npm plumbing.
148+
([@iarna](https://github.com/iarna))
149+
150+
* [`bc4b739`](https://github.com/npm/npm/commit/bc4b73911f58a11b4a2d28b49e24b4dd7365f95b)
151+
[#15089](https://github.com/npm/npm/pull/15089)
152+
Rename functions and variables in the module that computes what changes to
153+
make to your installation.
154+
([@iarna](https://github.com/iarna))
155+
156+
* [`2449f74`](https://github.com/npm/npm/commit/2449f74a202b3efdb1b2f5a83356a78ea9ecbe35)
157+
[#15089](https://github.com/npm/npm/pull/15089)
158+
When computing changes to make to your installation, use a function to add
159+
new actions to take instead of just pushing on a list.
160+
([@iarna](https://github.com/iarna))
161+
162+
#### IMPROVED LOGGING
163+
164+
* [`335933a`](https://github.com/npm/npm/commit/335933a05396258eead139d27eea3f7668ccdfab)
165+
[#15089](https://github.com/npm/npm/pull/15089)
166+
Log when we remove obsolete dependencies in the tree.
167+
([@iarna](https://github.com/iarna))
168+
169+
#### DOCUMENTATION
170+
171+
* [`33ca4e6`](https://github.com/npm/npm/commit/33ca4e6db3c1878cbc40d5e862ab49bb0e82cfb2)
172+
[#15157](https://github.com/npm/npm/pull/15157)
173+
Update `npm cache` docs to use more consistent language
174+
([@JonahMoses](https://github.com/JonahMoses))
175+
176+
#### DEPENDENCY UPDATES
177+
178+
* [`c2d22fa`](https://github.com/npm/npm/commit/c2d22faf916e8260136a1cc95913ca474421c0d3)
179+
[#15215](https://github.com/npm/npm/pull/15215)
180+
`nopt@4.0.1`:
181+
The breaking change is a small tweak to how empty string values are
182+
handled. See the brand-new
183+
[CHANGELOG.md for nopt](https://github.com/npm/nopt/blob/v4.0.1/CHANGELOG.md) for further
184+
details about what's changed in this release!
185+
([@adius](https://github.com/adius),
186+
[@samjonester](https://github.com/samjonester),
187+
[@elidoran](https://github.com/elidoran),
188+
[@helio](https://github.com/helio),
189+
[@silkentrance](https://github.com/silkentrance),
190+
[@othiym23](https://github.com/othiym23))
191+
* [`54d949b`](https://github.com/npm/npm/commit/54d949b05adefffeb7b5b10229c5fe0ccb929ac3)
192+
[npm/lockfile#24](https://github.com/npm/lockfile/pull/24)
193+
`lockfile@1.0.3`:
194+
Handled case where callback was not passed in by the user.
195+
([@ORESoftware](https://github.com/ORESoftware))
196+
* [`54acc03`](https://github.com/npm/npm/commit/54acc0389b39850c0725d0868cb5e61317b57503)
197+
`npmlog@4.0.2`:
198+
Documentation update.
199+
([@helio-frota](https://github.com/helio-frota))
200+
* [`57f4bc1`](https://github.com/npm/npm/commit/57f4bc1150322294c1ea0a287ad0a8e457c151e6)
201+
`osenv@0.1.4`:
202+
Test changes.
203+
([@isaacs](https://github.com/isaacs))
204+
* [`bea1a2d`](https://github.com/npm/npm/commit/bea1a2d0db566560e13ecc1d5f42e55811269c88)
205+
`retry@0.10.1`:
206+
No changes.
207+
([@tim-kos](https://github.com/tim-kos))
208+
* [`6749e39`](https://github.com/npm/npm/commit/6749e395f868109afd97f79d36507e6567dd48fb)
209+
[kapouer/marked-man#9](https://github.com/kapouer/marked-man/pull/9)
210+
`marked-man@0.2.0`:
211+
Add table support.
212+
([@gholk](https://github.com/gholk))
213+
1214
### v4.0.5 (2016-12-01)
2215

3216
It's that time of year! December is upon us, which means y'all are just going to
@@ -49,13 +262,13 @@ On to the actual changes!
49262
`EPERM` errors are Windows are now handled more gracefully. Windows users that
50263
tended to see these errors due to, say, an antivirus-induced race condition,
51264
should see them much more rarely, if at all.
52-
([@Kat Marchán](https://github.com/Kat Marchán))
265+
([@zkatr](https://github.com/zkat))
53266
* [`85b0174`](https://github.com/npm/npm/commit/85b0174ba9842e8e89f3c33d009e4b4a9e877c7d)
54267
`request@2.79.0`
55-
([@Kat Marchán](https://github.com/Kat Marchán))
268+
([@zkat](https://github.com/zkat))
56269
* [`9664d36`](https://github.com/npm/npm/commit/9664d36653503247737630440bc2ff657de965c3)
57270
`tap@8.0.1`
58-
([@Kat Marchán](https://github.com/Kat Marchán))
271+
([@zkat](https://github.com/zkat))
59272

60273
#### MISCELLANEOUS
61274

@@ -596,6 +809,7 @@ sending `Npm-Scope` and `Npm-In-CI` headers in outgoing requests.
596809

597810
* [`846f61c`](https://github.com/npm/npm/commit/846f61c1dd4a033f77aa736ab01c27ae6724fe1c)
598811
[npm/npm-registry-client#145](https://github.com/npm/npm-registry-client/pull/145)
812+
[npm/npm-registry-client#147](https://github.com/npm/npm-registry-client/pull/147)
599813
`npm-registry-client@7.3.0`:
600814
* Allow npm to add headers to outgoing requests.
601815
* Add `Npm-In-CI` header that reports whether we're running in CI.
Collapse file

‎deps/npm/doc/cli/npm-cache.md‎

Copy file name to clipboardExpand all lines: deps/npm/doc/cli/npm-cache.md
+3-2Lines changed: 3 additions & 2 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -11,10 +11,11 @@ npm-cache(1) -- Manipulates packages cache
1111
npm cache ls [<path>]
1212

1313
npm cache clean [<path>]
14+
aliases: npm cache clear, npm cache rm
1415

1516
## DESCRIPTION
1617

17-
Used to add, list, or clear the npm cache folder.
18+
Used to add, list, or clean the npm cache folder.
1819

1920
* add:
2021
Add the specified package to the local cache. This command is primarily
@@ -29,7 +30,7 @@ Used to add, list, or clear the npm cache folder.
2930
* clean:
3031
Delete data out of the cache folder. If an argument is provided, then
3132
it specifies a subpath to delete. If no argument is provided, then
32-
the entire cache is cleared.
33+
the entire cache is deleted.
3334

3435
## DETAILS
3536

Collapse file

‎deps/npm/doc/cli/npm-doctor.md‎

Copy file name to clipboard
+102Lines changed: 102 additions & 0 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,102 @@
1+
npm-doctor(1) -- Check your environments
2+
========================================================
3+
4+
## SYNOPSIS
5+
6+
npm doctor
7+
8+
## DESCRIPTION
9+
10+
`npm doctor` runs a set of checks to ensure that your npm installation has
11+
what it needs to manage your JavaScript packages. npm is mostly a standalone tool, but it does
12+
have some basic requirements that must be met:
13+
14+
+ Node.js and git must be executable by npm.
15+
+ The primary npm registry, `registry.npmjs.com`, or another service that uses
16+
the registry API, is available.
17+
+ The directories that npm uses, `node_modules` (both locally and globally),
18+
exist and can be written by the current user.
19+
+ The npm cache exists, and the package tarballs within it aren't corrupt.
20+
21+
Without all of these working properly, npm may not work properly. Many issues
22+
are often attributable to things that are outside npm's code base, so `npm
23+
doctor` confirms that the npm installation is in a good state.
24+
25+
Also, in addition to this, there are also very many issue reports due to using
26+
old versions of npm. Since npm is constantly improving, running `npm@latest` is
27+
better than an old version.
28+
29+
`npm doctor` verifies the following items in your environment, and if there are
30+
any recommended changes, it will display them.
31+
32+
### `npm ping`
33+
34+
By default, npm installs from the primary npm registry, `registry.npmjs.org`.
35+
`npm doctor` hits a special ping endpoint within the registry. This can also be
36+
checked with `npm ping`. If this check fails, you may be using a proxy that
37+
needs to be configured, or may need to talk to your IT staff to get access over
38+
HTTPS to `registry.npmjs.org`.
39+
40+
This check is done against whichever registry you've configured (you can see
41+
what that is by running `npm config get registry`), and if you're using a
42+
private registry that doesn't support the `/whoami` endpoint supported by the
43+
primary registry, this check may fail.
44+
45+
### `npm -v`
46+
47+
While Node.js may come bundled with a particular version of npm, it's the
48+
policy of the CLI team that we recommend all users run `npm@latest` if they
49+
can. As the CLI is maintained by a small team of contributors, there are only
50+
resources for a single line of development, so npm's own long-term support
51+
releases typically only receive critical security and regression fixes. The
52+
team believes that the latest tested version of npm is almost always likely to
53+
be the most functional and defect-free version of npm.
54+
55+
### `node -v`
56+
57+
For most users, in most circumstances, the best version of Node will be the
58+
latest long-term support (LTS) release. Those of you who want access to new
59+
ECMAscript features or bleeding-edge changes to Node's standard library may be
60+
running a newer version, and some of you may be required to run an older
61+
version of Node because of enterprise change control policies. That's OK! But
62+
in general, the npm team recommends that most users run Node.js LTS.
63+
64+
### `npm config get registry`
65+
66+
Some of you may be installing from private package registries for your project
67+
or company. That's great! Others of you may be following tutorials or
68+
StackOverflow questions in an effort to troubleshoot problems you may be
69+
having. Sometimes, this may entail changing the registry you're pointing at.
70+
This part of `npm doctor` just lets you, and maybe whoever's helping you with
71+
support, know that you're not using the default registry.
72+
73+
### `which git`
74+
75+
While it's documented in the README, it may not be obvious that npm needs Git
76+
installed to do many of the things that it does. Also, in some cases
77+
– especially on Windows – you may have Git set up in such a way that it's not
78+
accessible via your `PATH` so that npm can find it. This check ensures that Git
79+
is available.
80+
81+
### Permissions checks
82+
83+
* Your cache must be readable and writable by the user running npm.
84+
* Global package binaries must be writable by the user running npm.
85+
* Your local `node_modules` path, if you're running `npm doctor` with a project
86+
directory, must be readable and writable by the user running npm.
87+
88+
### Validate the checksums of cached packages
89+
90+
When an npm package is published, the publishing process generates a checksum
91+
that npm uses at install time to verify that the package didn't get corrupted
92+
in transit. `npm doctor` uses these checksums to validate the package tarballs
93+
in your local cache (you can see where that cache is located with `npm config
94+
get cache`, and see what's in that cache with `npm cache ls` – probably more
95+
than you were expecting!). In the event that there are corrupt packages in your
96+
cache, you should probably run `npm cache clean` and reset the cache.
97+
98+
## SEE ALSO
99+
100+
* npm-bugs(1)
101+
* npm-help(1)
102+
* npm-ping(1)

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.