Typo, "err" variable name should be "er".
publishConfig: conf.save() should save actual config, not pubConf

This avoids an error when the npm-registry-client gets a new token, and
attempts to call conf.save('user').  However, a publishConfig can't save
in this way, because it doesn't have a 'user' file source.

Binding the save to the parent config *does* avoid the error, but of course,
at the cost of making the save in this situation a no-op.
v1.3.26
npm-registry-client@0.3.5
npm-registry-client@0.3.6
factor out npm-install-checks

This removes the following checks from install.js, which are run
during installation:

- checkEngine
- checkPlatform
- checkCycle
- checkGit
add npm-install-checks@1.0.0
doc: new init.license default is "ISC"
Replace references to isaacs/npm with npm/npm.
raise node min. node version to 0.8 in package.json
Update npm-registry-mock to ~0.5.7
Show error to user on npm update

If a dependency is listed in the package.json, but the version does not
exist, show the user an error stating so.

Fixes #1770
Add CONTRIBUTING.md directing people to the wiki.
Document the 'depth' argument for `npm-ls'.
Verify ownership of git cloned/fetched files

In the case when people use `sudo npm install -g` some of the cloned git dependencies go to the npm cache. In this case when npm executes git clone or fetch, git sets ownership to root. This cases troubles when you try to do later `npm install` for dependencies which already under npm_cache/_git-remotes/ and has root ownership.

This change can cause performance degradation when you have a lot of git dependencies, because each time when you ask for git dependency - it will verify ownership first for all files under git folder. Better option will be to change ownership only for new fetched/cloned files.
Skip changing ownership on win32