deps: upgrade npm to 2.7.1

PR-URL: https://github.com/iojs/io.js/pull/1142
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Reviewed-By: Rod Vagg <rod@vagg.org>

6 files changed, 14 insertions, 6 deletions

diff --git a/deps/npm/man/man1/npm-install.1 b/deps/npm/man/man1/npm-install.1
index 3f01a6085f..e8416eb4c3 100644
--- a/deps/npm/man/man1/npm-install.1
+++ b/deps/npm/man/man1/npm-install.1
@@ -182,8 +182,8 @@ fetch the package by name if it is not valid\.
 .RE
 .IP \(bu 2
 \fBnpm install <githubname>/<githubrepo>\fR:
-  Install the package at \fBhttps://github\.com/githubname/githubrepo" by
-  attempting to clone it using\fRgit`\.
+  Install the package at \fBhttps://github\.com/githubname/githubrepo\fR by
+  attempting to clone it using \fBgit\fR\|\.
   Example:
 .P
 .RS 2
diff --git a/deps/npm/man/man1/npm-link.1 b/deps/npm/man/man1/npm-link.1
index 57bd6d9222..523731f3b5 100644
--- a/deps/npm/man/man1/npm-link.1
+++ b/deps/npm/man/man1/npm-link.1
@@ -45,7 +45,8 @@ npm link redis              # link\-install the package
 .RE
 .P
 Now, any changes to ~/projects/node\-redis will be reflected in
-~/projects/node\-bloggy/node_modules/node\-redis/
+~/projects/node\-bloggy/node_modules/node\-redis/\. Note that the link should
+be to the package name, not the directory name for that package\.
 .P
 You may also shortcut the two steps in one\.  For example, to do the
 above use\-case in a shorter way:
diff --git a/deps/npm/man/man1/npm-ls.1 b/deps/npm/man/man1/npm-ls.1
index 4f0b0e98c7..aeedc91e4c 100644
--- a/deps/npm/man/man1/npm-ls.1
+++ b/deps/npm/man/man1/npm-ls.1
@@ -23,7 +23,7 @@ For example, running \fBnpm ls promzard\fR in npm's source tree will show:
 .P
 .RS 2
 .nf
-npm@2.7.0 /path/to/npm
+npm@2.7.1 /path/to/npm
 └─┬ init\-package\-json@0\.0\.4
   └── promzard@0\.1\.5
 .fi
diff --git a/deps/npm/man/man1/npm-run-script.1 b/deps/npm/man/man1/npm-run-script.1
index b095ddb65f..7f94067d30 100644
--- a/deps/npm/man/man1/npm-run-script.1
+++ b/deps/npm/man/man1/npm-run-script.1
@@ -35,6 +35,13 @@ The \fBenv\fR script is a special built\-in command that can be used to list
 environment variables that will be available to the script at runtime\. If an
 "env" command is defined in your package it will take precedence over the
 built\-in\.
+.P
+In addition to the shell's pre\-existing \fBPATH\fR, \fBnpm run\fR adds
+\fBnode_modules/\.bin\fR to the \fBPATH\fR provided to scripts\. Any binaries provided by
+locally\-installed dependencies can be used without the \fBnode_modules/\.bin\fR
+prefix\. For example, if there is a \fBdevDependency\fR on \fBtap\fR in your package,
+you should write \fB"scripts": {"test": "tap test/\\*\.js"}\fR instead of \fB"scripts":
+{"test": "node_modules/\.bin/tap test/\\*\.js"}\fR to run your tests\.
 .SH SEE ALSO
 .RS 0
 .IP \(bu 2
diff --git a/deps/npm/man/man1/npm.1 b/deps/npm/man/man1/npm.1
index 4dc37963e9..4d42aec638 100644
--- a/deps/npm/man/man1/npm.1
+++ b/deps/npm/man/man1/npm.1
@@ -10,7 +10,7 @@ npm <command> [args]
 .RE
 .SH VERSION
 .P
-2.7.0
+2.7.1
 .SH DESCRIPTION
 .P
 npm is the package manager for the Node JavaScript platform\.  It puts
diff --git a/deps/npm/man/man3/npm.3 b/deps/npm/man/man3/npm.3
index cd71b11511..5df7b6a89e 100644
--- a/deps/npm/man/man3/npm.3
+++ b/deps/npm/man/man3/npm.3
@@ -20,7 +20,7 @@ npm\.load([configObject, ]function (er, npm) {
 .RE
 .SH VERSION
 .P
-2.7.0
+2.7.1
 .SH DESCRIPTION
 .P
 This is the API documentation for npm\.