deps: upgrade to npm 2.14.3 · nodejs/node@f4641ae

1+

### v2.14.3 (2015-09-03):

2+3+

#### TEAMS AND ORGS STILL BETA. CLI CODE STILL SOLID.

4+5+

Our closed beta for Teens and Orcs is happening! The web team is hard at work

6+

making sure everything looks pretty and usable and such. Once we fix things

7+

stemming from that beta, you can expect the feature to be available publicly.

8+

Some time after that, it'll even be available for free for FOSS orgs. It'll Be

9+

Done When It's Done™.

10+11+

#### OH GOOD, I CAN ACTUALLY UPSTREAM NOW

12+13+

Looks like last week's release foiled our own test suite when trying to upstream

14+

it to Node! Just a friendly reminder that no, `.npmrc` is no longer included

15+

then you pack/release a package! [@othiym23](https://github.com/othiym23) and

16+

[@isaacs](https://github.com/isaacs) managed to suss the really strange test

17+

failures resulting from that, and we've patched it in this release.

18+19+

* [`01a3428`](https://github.com/npm/npm/commit/01a3428534b754dca89a56fd1e49f55cb22f6f25)

20+

[#9476](https://github.com/npm/npm/issues/9476) test: Recreate missing

21+

`.npmrc` files when missing so downstream packagers can run tests on packed

22+

npm.

23+

([@othiym23](https://github.com/othiym23))

24+25+

#### TALKING ABOUT THE CHANGELOG IN THE CHANGELOG IS LIKE, POMO OR SOMETHING

26+27+

* [`c1e7a83`](https://github.com/npm/npm/commit/c1e7a83c0ae7aadf01aecc57cf8a0ae2009d4da8)

28+

[#9431](https://github.com/npm/npm/issues/9431) CHANGELOG: clarify

29+

windows-related nature of patch

30+

([@saper](https://github.com/saper))

31+32+

#### devDependencies UPDATED

33+34+

No actual dep updates this week, but we're bumping a couple of devDeps:

35+36+

* [`8454835`](https://github.com/npm/npm/commit/84548351bfd63e3e305d195abbcad24c6b7c3e8e)

37+

`tap@1.4.0`: Add `t.contains()` as alias to `t.match()`

38+

([@isaacs](https://github.com/isaacs))

39+

* [`13d2216`](https://github.com/npm/npm/commit/13d22161bcdeb6e1ed095d5ba2f77e6abfffa5eb)

40+

`deep-equal@1.0.1`: Make `null == undefined` in non-strict mode

41+

([@isaacs](https://github.com/isaacs))

42+143

### v2.14.2 (2015-08-27):

244345

#### GETTING THAT PESKY `preferGlobal` WARNING RIGHT

@@ -6,7 +48,8 @@ So apparently the `preferGlobal` option hasn't quite been warning correctly for

648

some time. But now it should be all better! tl;dr: if you try and install a

749

dependency with `preferGlobal: true`, and it's _not already_ in your

850

`package.json`, you'll get a warning that the author would really rather you

9-

install it with `--global`. :)

51+

install it with `--global`. This should prevent Windows PowerShell from thinking

52+

npm has failed just because of a benign warning.

10531154

* [`bbb25f3`](https://github.com/npm/npm/commit/bbb25f30d582f8979168c79233a9f8f840974f90)

1255

[#8841](https://github.com/npm/npm/issues/8841)