v5.0.1
Hey y'all! Hope you're enjoying the new npm!
As you all know, fresh software that's gone through major overhauls tends to miss a lot of spots the old one used to handle well enough, and npm@5
is no exception. The CLI team will be doing faster release cycles that go directly to the latest
tag for a couple of weeks while 5 stabilizes a bit and we're confident the common low-hanging fruit people are running into are all taken care of.
With that said: this is our first patch release! The biggest focus is fixing up a number of git-related issues that folks ran into right out the door. It also fixes other things, like some proxy/auth-related issues, and even has a neat speed boost! (You can expect more speed bumps in the coming releases as pending work starts landing, too!)
Thanks everyone who's been reporting issues and submitting patches!
BUGFIXES
e61e68dac
#16762 Makenpm publish
obey the--tag
flag again. (@zkat)923fd58d3
#16749 Speed up installations by nearly 20% by... removing one line of code. (hah) (@mikesherov)9aac984cb
Guard against a particular failure mode for a bug still being hunted down. (@iarna)80ab521f1
Pull in dependency updates for various core deps:- New
pacote
fixes several git-related bugs. ssri
update fixes crash on early node@4 versions.make-fetch-happen
update fixes proxy authentication issue.npm-user-validate
adds regex for blocking usernames with illegal chars.
(@zkat)
- New
7e5ce87b8
pacote@2.7.26
: Fixes various other git issues related to commit hashes. (@zkat)acbe85bfc
#16791npm view
was callingcb
prematurely and giving partial output when called in a child process. (@zkat)ebafe48af
#16750 Hamilpatch the Musical: Talk less, complete more. (@aredridel)
DOCUMENTATION
dc2823a6c
#16799 Document thatpackage-lock.json
is never allowed in tarballs. (@sonicdoe)f3cb84b44
#16771 Fixnpm -l
usage information for thetest
command. (@grawlinson)