|
| 1 | +### v2.14.12 (2015-11-19): |
| 2 | + |
| 3 | +#### TEEN ORCS AT THE GATES |
| 4 | + |
| 5 | +This week heralds the general release of the primary npm registry's [new |
| 6 | +support for private packages for |
| 7 | +organizations](http://blog.npmjs.org/post/133542170540/private-packages-for-organizations). |
| 8 | +For many potential users, it's the missing piece needed to make it easy for you |
| 9 | +to move your organization's private work onto npm. And now it's here! The |
| 10 | +functionality to support it has been in place in the CLI for a while now, |
| 11 | +thanks to [@zkat](https://github.com/zkat)'s hard work. |
| 12 | + |
| 13 | +During our final testing before the release, our ace support team member |
| 14 | +[@snopeks](https://github.com/snopeks) noticed that there had been some drift |
| 15 | +between the CLI team's implementation and what npm was actually preparing to |
| 16 | +ship. In the interests of everyone having a smooth experience with this |
| 17 | +_extremely useful_ new feature, we quickly made a few changes to square up the |
| 18 | +CLI and the web site experiences. |
| 19 | + |
| 20 | +* [`0e8b15e`](https://github.com/npm/npm/commit/0e8b15e9fbc89e31bd00e573b648846beddfb835) |
| 21 | + [#9327](https://github.com/npm/npm/issues/9327) `npm access` no longer has |
| 22 | + problems when run in a directory that doesn't contain a `package.json`. |
| 23 | + ([@othiym23](https://github.com/othiym23)) |
| 24 | +* [`c4e939c`](https://github.com/npm/npm/commit/c4e939c1d493601d25dcb88e6ffcca73076fd3fd) |
| 25 | + [npm/npm-registry-client#126](https://github.com/npm/npm-registry-client/issues/126) |
| 26 | + `[email protected]`: Allow the CLI to grant, revoke, and list |
| 27 | + permissions on unscoped (public) packages on the primary registry. |
| 28 | + ([@othiym23](https://github.com/othiym23)) |
| 29 | + |
| 30 | +#### A BRIEF NOTE ON NPM'S BACKWARDS COMPATIBILITY |
| 31 | + |
| 32 | +We don't often have much to say about the changes we make to our internal |
| 33 | +testing and tooling, but I'm going to take this opportunity to reiterate that |
| 34 | +npm tries hard to maintain compatibility with a wide variety of Node versions. |
| 35 | +As this change shows, we want to ensure that npm works the same across: |
| 36 | + |
| 37 | +* Node.js 0.8 |
| 38 | +* Node.js 0.10 |
| 39 | +* Node.js 0.12 |
| 40 | +* the latest io.js release |
| 41 | +* Node.js 4 LTS |
| 42 | +* Node.js 5 |
| 43 | + |
| 44 | +Contributors who send us pull requests often notice that it's very rare that |
| 45 | +our tests pass across all of those versions (ironically, almost entirely due to |
| 46 | +the packages we use for testing instead of any issues within npm itself). We're |
| 47 | +currently beginning an effort, lasting the rest of 2015, to clean up our test |
| 48 | +suite, and not only get it passing on all of the above versions of Node.js, but |
| 49 | +working solidly on Windows as well. This is a compounding form of technical |
| 50 | +debt that we're finally paying down, and our hope is that cleaning up the tests |
| 51 | +will produce a more robust CLI that's a lot easier to write patches for. |
| 52 | + |
| 53 | +* [`d743620`](https://github.com/npm/npm/commit/d743620a0005213a65d25de771661b4d48a09717) |
| 54 | + [#10233](https://github.com/npm/npm/issues/10233) Update Node.js versions |
| 55 | + that Travis uses to test npm. ([@iarna](https://github.com/iarna)) |
| 56 | + |
| 57 | +#### TYPOS IN THE LICENSE, OH MY |
| 58 | + |
| 59 | +* [`58ac241`](https://github.com/npm/npm/commit/58ac241f556b2c202a8ee33321965e2540361ca7) |
| 60 | + [#10478](https://github.com/npm/npm/issues/10478) Correct two typos in npm's |
| 61 | + LICENSE. ([@jorrit](https://github.com/jorrit)) |
| 62 | + |
| 63 | +### v2.14.11 (2015-11-12): |
| 64 | + |
| 65 | +#### ASK FOR NOTHING, GET LATEST |
| 66 | + |
| 67 | +When you run `npm install foo`, you probably expect that you'll get the |
| 68 | +`latest` version of `foo`, whatever that is. And good news! That's what this |
| 69 | +change makes it do. |
| 70 | + |
| 71 | +We _think_ this is what everyone wants, but if this causes problems for you, we |
| 72 | +want to know! If it proves problematic for people we will consider reverting it |
| 73 | +(preferrably before this becomes `npm@latest`). |
| 74 | + |
| 75 | +Previously, when you ran `npm install foo` we would act as if you typed `npm |
| 76 | +install foo@*`. Now, like any range-type specifier, in addition to matching the |
| 77 | +range, it would also have to be `<=` the value of the `latest` dist-tag. |
| 78 | +Further, it would exclude prerelease versions from the list of versions |
| 79 | +considered for a match. |
| 80 | + |
| 81 | +This worked as expected most of the time, unless your `latest` was a prerelease |
| 82 | +version, in which case that version wouldn't be used, to everyone's surprise. |
| 83 | + |
| 84 | +* [`6f0a646`](https://github.com/npm/npm/commit/6f0a646cd865b24fe3ff25365bf5421780e63e01) |
| 85 | + [#10189](https://github.com/npm/npm/issues/10189) `[email protected]`: |
| 86 | + Change the default version from `*` to `latest`. |
| 87 | + ([@zkat](https://github.com/zkat)) |
| 88 | + |
| 89 | +#### LICENSE CLARIFICATION |
| 90 | + |
| 91 | +* [`54a9046`](https://github.com/npm/npm/commit/54a90461f068ea89baa5d70248cdf1581897936d) |
| 92 | + [#10326](https://github.com/npm/npm/issues/10326) Clarify what-all is covered |
| 93 | + by npm's license and point to the registry's terms of use. |
| 94 | + ([@kemitchell](https://github.com/kemitchell)) |
| 95 | + |
| 96 | +#### CLOSER TO GREEN TRAVIS |
| 97 | + |
| 98 | +* [`28efd3d`](https://github.com/npm/npm/commit/28efd3d7dfb2fa3755076ae706ea4d38c6ee6900) |
| 99 | + [#10232](https://github.com/npm/npm/issues/10232) `[email protected]`: Downgrade |
| 100 | + nock to a version that doesn't depend on streams2 in core so that more of our |
| 101 | + tests can pass in 0.8. ([@iarna](https://github.com/iarna)) |
| 102 | + |
| 103 | +#### A BUG FIX |
| 104 | + |
| 105 | +* [`eacac8f`](https://github.com/npm/npm/commit/eacac8f05014d15217c3d8264d0b00a72eafe2d2) |
| 106 | + [#9965](https://github.com/npm/npm/issues/9965) Fix a corrupt `package.json` |
| 107 | + file introduced by a merge conflict in |
| 108 | + [`022691a`](https://github.com/npm/npm/commit/022691a). |
| 109 | + ([@waynebloss](https://github.com/waynebloss)) |
| 110 | + |
| 111 | +#### A DEPENDENCY UPGRADE |
| 112 | + |
| 113 | +* [`ea7d8e0`](https://github.com/npm/npm/commit/ea7d8e00a67a3d5877ed72c9728909c848468a9b) |
| 114 | + [npm/nopt#51](https://github.com/npm/nopt/pull/51) `[email protected]`: Allow |
| 115 | + types checked to be validated by passed-in name in addition to the JS name of |
| 116 | + the type / class. ([@wbecker](https://github.com/wbecker)) |
| 117 | + |
| 118 | +### v2.14.10 (2015-11-05): |
| 119 | + |
| 120 | +There's nothing in here that that isn't in the `[email protected]` release notes, but |
| 121 | +all of the commit shasums have been adjusted to be correct. Enjoy! |
| 122 | + |
| 123 | +#### BUG FIXES VIA DEPENDENCY UPDATES |
| 124 | + |
| 125 | +* [`204c558`](https://github.com/npm/npm/commit/204c558c06637a753c0b41d0cf19f564a1ac3715) |
| 126 | + [#8640](https://github.com/npm/npm/issues/8640) |
| 127 | + [npm/normalize-package-data#69](https://github.com/npm/normalize-package-data/pull/69) |
| 128 | + `[email protected]`: Fix a bug where if you didn't specify the |
| 129 | + name of a scoped module's binary, it would install it such that it was |
| 130 | + impossible to call it. ([@iarna](https://github.com/iarna)) |
| 131 | +* [`bbdf4ee`](https://github.com/npm/npm/commit/bbdf4ee0a3cd12be6a2ace255b67d573a72f1f8f) |
| 132 | + [npm/fstream-npm#14](https://github.com/npm/fstream-npm/pull/14) |
| 133 | + `[email protected]`: Only filter `config.gypi` when it's in the build |
| 134 | + directory. ([@mscdex](https://github.com/mscdex)) |
| 135 | +* [`d82ff81`](https://github.com/npm/npm/commit/d82ff81403e906931fac701775723626dcb443b3) |
| 136 | + [npm/fstream-npm#15](https://github.com/npm/fstream-npm/pull/15) |
| 137 | + `[email protected]`: Stop including directories that happened to have names |
| 138 | + matching whitelisted npm files in npm module tarballs. The most common cause |
| 139 | + was that if you had a README directory then everything in it would be |
| 140 | + included if wanted it or not. ([@taion](https://github.com/taion)) |
| 141 | + |
| 142 | +#### DOCUMENTATION FIXES |
| 143 | + |
| 144 | +* [`16361d1`](https://github.com/npm/npm/commit/16361d122f2ff6d1a4729c66153b7c24c698fd19) |
| 145 | + [#10036](https://github.com/npm/npm/pull/10036) Fix typo / over-abbreviation. |
| 146 | + ([@ifdattic](https://github.com/ifdattic)) |
| 147 | +* [`d1343dd`](https://github.com/npm/npm/commit/d1343dda42f113dc322f95687f5a8c7d71a97c35) |
| 148 | + [#10176](https://github.com/npm/npm/pull/10176) Fix broken link, scopes => |
| 149 | + scope. ([@ashleygwilliams](https://github.com/ashleygwilliams)) |
| 150 | +* [`110663d`](https://github.com/npm/npm/commit/110663d000a3908a4853393d9abae481700cf4dc) |
| 151 | + [#9460](https://github.com/npm/npm/issue/9460) Specifying the default command |
| 152 | + run by "npm start" and the fact that you can pass it arguments. |
| 153 | + ([@JuanCaicedo](https://github.com/JuanCaicedo)) |
| 154 | + |
| 155 | +#### DEPENDENCY UPDATES FOR THEIR OWN SAKE |
| 156 | + |
| 157 | +* [`7476d2d`](https://github.com/npm/npm/commit/7476d2d31552a41671c425aa7fcc2844e0381008) |
| 158 | + [npm/npmlog#19](https://github.com/npm/npmlog/pull/19) |
| 159 | + `[email protected]`: Make it possible to emit log messages with `error` as the |
| 160 | + prefix. |
| 161 | + ([@bengl](https://github.com/bengl)) |
| 162 | +* [`6ca7888`](https://github.com/npm/npm/commit/6ca7888862cfe8bf802dc7c66632c102acd94cf5) |
| 163 | + `[email protected]`: Minor cleanups. |
| 164 | + ([@KenanY](https://github.com/KenanY)) |
| 165 | + |
1 | 166 | ### v2.14.9 (2015-10-29): |
2 | 167 |
|
3 | 168 | There's still life in `npm@2`, but for now, enjoy these dependency upgrades! |
|
0 commit comments