|
| 1 | +### v4.2.0 (2017-01-26): |
| 2 | + |
| 3 | +Hi all! I'm Kat, and I'm currently sitting in a train traveling at ~300km/h |
| 4 | +through Spain. So clearly, this release should have *something* to do with |
| 5 | +speed. And it does! Heck, with this release, you could say we're really |
| 6 | +_blazing_, even. 🌲🔥😏 |
| 7 | + |
| 8 | +#### IMPROVED CLI SEARCH~ |
| 9 | + |
| 10 | +You might recall if you've been keeping up that one of the reasons for a |
| 11 | +semver-major bump to `npm@4` was an improved CLI search (read: no longer blowing |
| 12 | +up Node). The work done for that new search system, while still relying on a |
| 13 | +full metadata download and local search, was also meant to act as groundwork for |
| 14 | +then-ongoing work on a brand-new, smarter search system for npm. Shortly after |
| 15 | +`npm@4` came out, the bulk of the server-side work was done, and with this |
| 16 | +release, the npm CLI has integrated use of the new endpoint for high-quality, |
| 17 | +fast-turnaround searches. |
| 18 | + |
| 19 | +No, seriously, it's *fast*. And *relevant*: |
| 20 | + |
| 21 | +[](https://github.com/npm/npm/pull/15481) |
| 22 | + |
| 23 | +Give it a shot! And remember to check out the new website version of the search, |
| 24 | +too, which uses the same backend as the CLI now. 🎉 |
| 25 | + |
| 26 | +Incidentally, the backend is a public service, so you can write your own search |
| 27 | +tools, be they web-based, CLI, or GUI-based. You can read up on the [full |
| 28 | +documentation for the search |
| 29 | +endpoint](https://github.com/npm/registry/blob/master/docs/REGISTRY-API.md#get-v1search), |
| 30 | +and let us know about the cool things you come up with! |
| 31 | + |
| 32 | +* [`ce3ca51`](https://github.com/npm/npm/commit/ce3ca51ca2d60e15e901c8bf6256338e53e1eca2) |
| 33 | + [#15481](https://github.com/npm/npm/pull/15481) |
| 34 | + Add an internal `gunzip-maybe` utility for optional gunzipping. |
| 35 | + ([@zkat](https://github.com/zkat)) |
| 36 | +* [`e322932`](https://github.com/npm/npm/commit/e3229324d507fda10ea9e94fd4de8a4ae5025c75) [`a53055e`](https://github.com/npm/npm/commit/a53055e423f1fe168f05047aa0dfec6d963cb211) [`a1f4365`](https://github.com/npm/npm/commit/a1f436570730c6e4a173ca92d1967a87c29b7f2d) [`c56618c`](https://github.com/npm/npm/commit/c56618c62854ea61f6f716dffe7bcac80b5f4144) |
| 37 | + [#15481](https://github.com/npm/npm/pull/15481) |
| 38 | + Add support for using the new npm search endpoint for fast, quality search |
| 39 | + results. Includes a fallback to "classic" search. |
| 40 | + ([@zkat](https://github.com/zkat)) |
| 41 | + |
| 42 | +#### WHERE DID THE DEBUG LOGS GO |
| 43 | + |
| 44 | +This is another pretty significant change: Usually, when the npm process |
| 45 | +crashed, you would get an `npm-debug.log` in your current working directory. |
| 46 | +This debug log would get cleared out as soon as you ran npm again. This was a |
| 47 | +bit annoying because 1) you would get a random file in your `git status` that |
| 48 | +you might accidentally commit, and 2) if you hit a hard-to-reproduce bug and |
| 49 | +instinctually tried again, you would no longer have access to the repro |
| 50 | +`npm-debug.log`. |
| 51 | + |
| 52 | +So now, any time a crash happens, we'll save your debug logs to your cache |
| 53 | +folder, under `_logs` (`~/.npm` on *nix, by default -- use `npm config get |
| 54 | +cache` to see what your current value is). The cache will now hold a |
| 55 | +(configurable) number of `npm-debug.log` files, which you can access in the |
| 56 | +future. Hopefully this will help clean stuff up and reduce frustration from |
| 57 | +missed repros! In the future, this will also be used by `npm report` to make it |
| 58 | +super easy to put up issues about crashes you run into with npm. 💃🕺🏿👯♂️ |
| 59 | + |
| 60 | +* [`04fca22`](https://github.com/npm/npm/commit/04fca223a0f704b69340c5f81b26907238fad878) |
| 61 | + [#11439](https://github.com/npm/npm/pull/11439) |
| 62 | + Put debug logs in `$(npm get cache)/_logs` and store multiple log files. |
| 63 | + ([@KenanY](https://github.com/KenanY)) |
| 64 | + ([@othiym23](https://github.com/othiym23)) |
| 65 | + ([@isaacs](https://github.com/isaacs)) |
| 66 | + ([@iarna](https://github.com/iarna)) |
| 67 | + |
| 68 | +#### DOCS |
| 69 | + |
| 70 | +* [`ae8e71c`](https://github.com/npm/npm/commit/ae8e71c2b7d64d782af287a21e146d7cea6e5273) |
| 71 | + [#15402](https://github.com/npm/npm/pull/15402) |
| 72 | + Add missing backtick in one of the `npm doctor` messages. |
| 73 | + ([@watilde](https://github.com/watilde), [@charlotteis](https://github.com/charlotteis)) |
| 74 | +* [`821fee6`](https://github.com/npm/npm/commit/821fee6d0b12a324e035c397ae73904db97d07d2) |
| 75 | + [#15480](https://github.com/npm/npm/pull/15480) |
| 76 | + Clarify that unscoped packages can depend on scoped packages and vice-versa. |
| 77 | + ([@chocolateboy](https://github.com/chocolateboy)) |
| 78 | +* [`2ee45a8`](https://github.com/npm/npm/commit/2ee45a884137ae0706b7c741c671fef2cb3bac96) |
| 79 | + [#15515](https://github.com/npm/npm/pull/15515) |
| 80 | + Update minimum supported Node version number in the README to `node@>=4`. |
| 81 | + ([@watilde](https://github.com/watilde)) |
| 82 | +* [`af06aa9`](https://github.com/npm/npm/commit/af06aa9a357578a8fd58c575f3dbe55bc65fc376) |
| 83 | + [#15520](https://github.com/npm/npm/pull/15520) |
| 84 | + Add section to `npm-scope` docs to explain that scope owners will own scoped |
| 85 | + packages with that scope. That is, user `@alice` is not allowed to publish to |
| 86 | + `@bob/my-package` unless explicitly made an owner by user (or org) `@bob`. |
| 87 | + ([@hzoo](https://github.com/hzoo)) |
| 88 | +* [`bc892e6`](https://github.com/npm/npm/commit/bc892e6d07a4c6646480703641a4d71129c38b6d) |
| 89 | + [#15539](https://github.com/npm/npm/pull/15539) |
| 90 | + Replace `http` with `https` and fix typos in some docs. |
| 91 | + ([@watilde](https://github.com/watilde)) |
| 92 | +* [`1dfe875`](https://github.com/npm/npm/commit/1dfe875b9ac61a0ab9f61a2eab02bacf6cce583c) |
| 93 | + [#15545](https://github.com/npm/npm/pull/15545) |
| 94 | + Update Node.js download link to point to the right place. |
| 95 | + ([@watilde](https://github.com/watilde)) |
| 96 | + |
| 97 | +#### DEPENDENCIES |
| 98 | + |
| 99 | + * [`b824bfb`](https://github.com/npm/npm/commit/b824bfbeb2d89c92762e9170b026af98b5a3668a) |
| 100 | + |
| 101 | + * [`81ea3e8`](https://github.com/npm/npm/commit/81ea3e8e4ea34cd9c2b418512dcb508abcee1380) |
| 102 | + |
| 103 | + |
| 104 | +#### MISC |
| 105 | + |
| 106 | +* [`98df212`](https://github.com/npm/npm/commit/98df212a91fd6ff4a02b9cd247f4166f93d3977a) |
| 107 | + [#15492](https://github.com/npm/npm/pull/15492) |
| 108 | + Update the "master" node version used for AppVeyor to `node@7`. |
| 109 | + ([@watilde](https://github.com/watilde)) |
| 110 | +* [`d75fc03`](https://github.com/npm/npm/commit/d75fc03eda5364f12ac266fa4f66e31c2e44e864) |
| 111 | + [#15413](https://github.com/npm/npm/pull/15413) |
| 112 | + `npm run-script` now exits with the child process' exit code on exit. |
| 113 | + ([@kapals](https://github.com/kapals)) |
| 114 | + |
1 | 115 | ### v4.1.2 (2017-01-12) |
2 | 116 |
|
3 | 117 | We have a twee little release this week as we come back from the holidays. |
|
0 commit comments