npm-registry-client@2.0.3
1.4.21
upgrade npmconf and init-package-json

Adds support for 'init.version' config, and falling back to _auth
config as default auth when using default registry.
Remove win from documented loglevels
npmconf@2.0.3
1.5.0-alpha-4
Add note about pre- & post- commands be invoked for custom scripts as well
Display usage for cache without arguments
test: make config-meta test work on Windows
path.basename(pp) => npa(pkgId).name (fixes #5758)
fstream@0.1.29
mkdirp@0.5.0
test against npm-registry-couchapp@2.4.3
making it so that you can pass arguments to run-scripts.
link binaries for scoped packages (fixes #5748)
github-url-from-git@1.2.0
2.0.0-alpha-5
test: fix ignore-install-link on windows

Was relying on using an administrator-owned global folder, which is a pita.
npm-package-arg@2.0.1
Don't squash execute perms in _git-remotes/ dir

A previous fix for https://github.com/npm/npm/issues/3117
explicitly set the permissions for all files to a hard-coded
value, regardless of what the permissions were previously.

This changes that behavior to *add* the permissions that were
previously being *set* so that existing execute permissions are
maintained.

This is a redo of the much more blunt solution attempted in
https://github.com/npm/npm/pull/5728
thanks to some very helpful feedback from @othiym23