nopt@2.2.0
glob@3.2.8
outdated: optimize out an extra HTTP request

While the request to foo/latest will be less data over the wire,
it's also much less likely to be cached by the registry CDN.

This, it's more likely to be a trip to the origin server, which is
much slower than serving out of the CDN.

Additionally, we can then use that data object to check the
versions hash here in outdated.js, rather than doing a full tgz
download and unpack for 'cache.add'.
docs: More npm, Inc. copy updates
Respect --color settings in outdated.

Fixes #4493
more legible error message in config.get/set

Test added by @isaacs
Closes #4458
doc: Update AUTHORS doc
doc: formatting
npm outdated --parseable fix
test: Add test for outdated --parseable
clean git url before locking

modifying the url inside the locked section was causing unlock() to be
called with a different value than was used in lock()
assert that only files we locked get unlocked
Add Neil Gentleman to AUTHORS file
serialize shrinkwrap payload in order

JavaScript objects will serialize in an arbitrary key order because key
enumeration is not well defined.

To avoid this we sort the keys and create a fresh object in a specific
order. v8 will serialize this object in a consistent fashion.

The problem is *probably* caused because `commands.ls` will write keys
to the `pkginfo` in arbitrary order based on disk IO latency and such
graceful-fs@2.0.2

Related to #4557, as this will enforce sorting of all
readdir() calls, so dependencies etc will be in consistent
orders on systems that don't sort dir listings internally
glob: revert to 3.2.7 to avoid mark:true regression
v1.4.3
uid-number@0.0.4
Document the --tag option of npm-publish
alias 't' to 'test'

For @maxogden