You can clone with
HTTPS or Subversion.
Check that the `error` property of parsed is not an `object`, which may
be a valid value
bail out on error status code even without message
less funky formatting
dealing with numeric defaults is hard
retry module wants `retries`, not `count`
Fetching a tarball from GitHub's API endpoints returns a 415 if the request
doesn't accept json.
request will handle proxy by itself (fixes 82)
fix publish for modules where name matches core
bye bye, unused functions
bugs, you were too good for this world
upload was also too beautiful for this world
decouple configuration from npm / npmconf
remove all dependencies on npm's cache
getAll logic → npm's own update-index.js
removed dead config
rework API for consistency
updated (with tests and up-to-date documentation!):
Nothing uses these functions anymore, so it's safe to remove them.
explicitly pass credentials
Bump request version to >=2.45.0
make retry dep a range
npmconf is gone, so don't peerDep on it
use always-auth from credentials instead of config
This depends on new behavior in npmconf!
revert changes to fetch-basic.js
error when not retrying fetches
also rework tests to cover more code paths
add test for new error handling
Include extra data on errors other than 404
'retrier' made @timoxley sad :(
Also fits with the theme of making diagnostic output clearer.