- Notifications
You must be signed in to change notification settings - Fork3k
v2.14.16
Compare
Good to see you all again! It's been a while since we had an LTS release, and the team continues to work hard to both get the issue tracker under control, and get our test suite to be awesome and reliable.
This is also the first LTS release of this year.
We're gonna have an interesting time -- most of our focus this year will be around stability and maintainability of the CLI, so you might actually end up seeing a number of updates even over here, just for the sake of making sure we're stable, that bugs get fixed, and tests have proper coverage.
What better way to start this effort, then, than getting Travis tests green, fix a few things here and there, and tweak a bunch of documentation? 😁
FIX ALL THE BUGS AND TWEAK ALL THE THINGS
24b13fb
#11158 Fix custom node-gyp env var quoting on Windows. (@orangemocha)e2503f2
#11142 Fix race condition withcorrectMkdir
in the cache directory. (@Jimbly)5c0e4c4
#10940 Ignore failures replacingpackage.json
. writeFileAtomic is not atomic in Windows, it fails if the file is being accessed concurrently. (@orangemocha)2c44d8d
#10903 Add tests fornpm adduser --scope
. (@ekmartin)4cb25d0
#10903 Add a message informing users when they have been successfully logged in. (@ekmartin)fe3ec6d
#10628 Tell users how to open an issue with a package that has errored. (@trodrigues)
DOCS DOCS DOCS
We got a TON of lovely documentation patches, too! Thanks all for submitting!
22482a1
#11188 Briefly explain what's included when you publish. (@beaugunderson)fa47724
#11150 Advise use of--depth Infinity
instead of--depth 9999
innpm update
. (@halhenke)248ddfe
#11130 Nuke "using npm programmatically" section from README. The programmatic npm API is unsupported, and is not guaranteed not to break in non-major versions. Removing this section so newcomers aren't encouraged to discover or use it. (@ljharb)ae9c452
#11128 Add link to local paths section indocs forpackage.json
. (@orangejulius)663a8c6
#11044 Update default value documentation for the color option in npm's config. (@scottaddie)5c1dda0
#11037 Correct the name property max length constraint verbiage. (@scottaddie)8288365
#10990 Update folder docs to reflect that process.installPrefix was removed as of 0.8.x. (@jeffmcmahan)61d63fa
#10790 Clarify thatnpm install foo
is the same asnpm install foo@latest
now. (@cvrebert)442c920
#10789 Link over tonpm-dist-tag(1)
innpm install
docs when they talk about thepkg@<tag>
syntax. (@cvrebert)dca7a5e
#10788 Link to tag docs in docs fornpm publish --tag
. (@cvrebert)a72904e
#10787 Explain why thelatest
tag matters. (@cvrebert)9d0697a
#10785 Replace some quite marks innpm dist-tag
docs for the sake of consistency. (@cvrebert)
I REALLY LIKE GREEN. CAN YOU TELL?
So Travis is all green now onnpm@2
, thanks to the removal of nock and a few other test suite tweaks. This is a fantastic step towards making sure we can all have confidence in our test suite! 🎉
64995be
75ab216
a9f6fe9
649c193
94cb05e
6541690
255be6f
9e84fa4
8a587b0
bf812a5
#10903 Get rid of nock from tests, and get Travis green. (@zkat and@iarna)70a5310
npm-registry-couchapp@2.6.12
: Better 0.8 compatibility, and ability to run in travis docker stuff. This means the test suite should run a lot faster, too! (@iarna)28fae39
Get rid of sudo, for Travis! (@zkat)
Assets2
Uh oh!
There was an error while loading.Please reload this page.