npm-faq.md: mention scoped pkgs in namespace Q

Add some text describing the npm 2.x.x scoped package feature.
init-package-json@1.1.2

Handle both init-author-name and init.author.name. For #6642.
only add _resolved for local deps with path
`adduser.js` is the name of the module
document commit-ish with GitHub URLs (fixes #6409)

Implement doc change suggested in issue 6409, explicitly mention
that commit-ish suffixes can be attached to github URLs in dependencies.
npm run no longer fails silently (closes #2959)

if the missing command is "test", logs a text error, otherwise creates an actual error.
fixed so test always "passes" and doesn't exit
Fix ignore-scripts test
Add unit tests
include command in spawn errors (fixes #3908)

factor to centralize
wrap child, make it aware of filename
update changelog for npm@2.1.8
2.1.8
npm-adduser update doc re email

typo
README.md: link to Windows upgrade instructions
replace proxy settings in defaults with `null`.

The `mikeal/request` package already handles proxy support, including
environment variables `http_proxy`, `https_proxy`, `no_proxy`, and
variants. `npm` should let `request` take care of proxying based on
environment variables and only set proxy values if `.npmrc` has a proxy
specified. By passing a proxy to request, request will always use that
proxy setting and will not honor `no_proxy` settings. This will enable
the use of a private npm repository that is within a corporate firewall.

See https://github.com/npm/npm/issues/6524 for more details.
update config docs with new https_proxy and proxy default values
npm-registry-client@4.0.2

proxy via request and environment variables more transparently
isntall there really is?

Who, that little guy? I wouldn't worry about that little guy.
simplify normalization
warn on fetch failure (closes #6644)
prevent the auth regression fixed by 7719cfd

Make sure that the correct credentials are being used for auth.
fs-vacuum@1.2.2

Don't complain when somebody writes to a path you're vacuuming after
you've checked that it's empty, just log and bail out. Also log when
somebody else wins the race to remove the empty directory.
never remove project directories (fixes #5754)

A failed install could cause the removal of an empty (new) project
directory because fs-vacuum wasn't being told where to stop vacuuming up
empty directories. Pass in the project path to provide a hard
backstop for fs-vacuum, and be more careful to specify which things
should be gently removed during unbuilding.