glob@4.0.3
v1.4.18
bump nopt and npmconf

Fixes #5591

The root cause here is that a change from 022 (a number in octal literal
format) to '022' (a string) caused the string to later be interpreted as
a decimal number, making for some wacky umask values.

Solution is multipart.

First, use the actual process.umask() value from the user's environment.
This is almost certainly what they want anyway.

Second, validate all default values just like we do with user- supplied
values, rather than trusting them to never be wrong.  This would've
found the problem much sooner, while in dev.

This second part requires that we allow a value of null for 'path' type
args, allow 'undefined' for the 'local-address' config, and avoid
looking up a cafile of 'null', all of which are good hygenic things to
add defense-in-depth anyway.
relative URLS for working non-root registry URLS
v1.4.19
Merge branch 'v1.4'

Conflicts:
	package.json
don't publish as latest until ready
capture and store bearer token
install working version of npm-registry-client
first piece of @org/package module specifiers
update npm-registry-client othiym23/multi-registry
publish to scoped registries
@scope:registry-base-url → @scope:registry
scope token to the registry
update npm-registry-client
update read-package-json to othiym23/scoped
use --scope to map scope to registry
chasing down errant uses of old auth, part 1
npmconf@npm/npmconf#othiym23/new-credentials
username and email are now always scoped to a registry