The npm blog has been discontinued.
A little release to tide you over while we hammer out the last bits for npm@5.
name:prompt is now
package name:to make this less ambiguous for new users.
The default package name is now a valid package name. For example: If your package directory has mixed case, the default package name will be all lower case.
npm versionso that you can use
npm versionto run your version lifecycles and tag your git repo without actually changing the version number in your
f5e8becd0Timing has been added throughout the install implementation. You can see it by running a command with
--loglevel=timing. You can also run commands with
--timingwhich will write an
npm-debug.logeven on success and add an entry to
_timing.jsonin your cache with the timing information from that run. (@iarna)
9c860f2ed#16021 Fix a crash in
npm doctorwhen used with a registry that does not support the
pingAPI endpoint. (@watilde)
65b9943e9#16364 Shorten the ELIFECYCLE error message. The shorter error message should make it much easier to discern the actual cause of the error. (@j-f1)
firstname.lastname@example.org: Fix flashing of the progress bar when your terminal is very narrow. (@iarna)
email@example.com: Wait for
fsyncto complete before considering our file written to disk. This will improve certain sorts of Windows diagnostic problems.
2afa9240c#16336 Don’t ham-it-up when expecting JSON. (@bdukes)
566f3eebe#16296 Use a single convention when referring to the
<command>you’re running. (@desfero)
ccbb94934#16267 Fix a missing space in the example package.json. (@famousgarkin)