write-file-atomic@1.1.0

use graceful-fs like everything else
update changelog for npm@2.0.2
2.0.2
update docs, fixes #4343
fixes #5867, replaces #5790: no git hooks

Specify dummy template dir when cloning to prevent copying hooks.
doc: spelling error
add `npm view .`

Fixes #5520

This adds back the ability to run `npm view .`

Includes multiple tests for `npm view`
marked-man@0.1.4

Fixes formatting of synopsis blocks in man docs.
Re-apply a71615a. Fixes #3265 again, with a test!

a71615a accidentally got reverted by 355bb7e, which split the changed
file into multiple files.

Original commit message:

    Check SHA before using files from cache

    Fixes #3265.

    Because 'npm install' *always* writes every package to the cache (even
    if it isn't installed from the registry) before installing it, it's easy
    to end up in a situation where "npm install foo" installs something
    other than the appropriate version from the registry.  eg:

      npm cache clean
      # Install a fork of version 0.0.1:
      npm install https://github.com/glasser/npm-cache-corruption/tarball/93c447e
      rm -rf node_modules
      # Before this commit, this would install the same fork as above
      npm install npm-cache-corruption
Fix development dependency is preferred over dependency.

If a dependency occurs in both the `dependencies` and the `devDependencies`
sections of package.json, npm should prefer the version from the `dependencies`
section since it is what is used when installed with `--production`

A warning is issued with information about what version is used.
npm rm <noargs> should globally remove the local pkg

Fix #4005 #6248

What's interesting is that the comment in the code seems to indicate
that this was *always* the intent.  But somewhere along the line, that
seems to have broken.

This makes 'npm link' be un-done by running 'npm unlink'.