summaryrefslogtreecommitdiff
path: root/deps/npm/man/man1/npm-README.1
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/man/man1/npm-README.1')
-rw-r--r--deps/npm/man/man1/npm-README.115
1 files changed, 7 insertions, 8 deletions
diff --git a/deps/npm/man/man1/npm-README.1 b/deps/npm/man/man1/npm-README.1
index 644147b483..09c3805fed 100644
--- a/deps/npm/man/man1/npm-README.1
+++ b/deps/npm/man/man1/npm-README.1
@@ -1,4 +1,4 @@
-.TH "NPM" "1" "April 2016" "" ""
+.TH "NPM" "1" "May 2016" "" ""
.SH "NAME"
\fBnpm\fR \- a JavaScript package manager
.P
@@ -80,13 +80,12 @@ run npm commands by doing \fBnode cli\.js <cmd> <args>\fP\|\. (This is helpful
for testing, or running stuff without actually installing npm itself\.)
.SH Windows Install or Upgrade
.P
-You can download a zip file from https://github\.com/npm/npm/releases, and
-unpack it in the \fBnode_modules\\npm\\\fP folder inside node's installation folder\.
-.P
-To upgrade to npm 2, follow the Windows upgrade instructions in
-the npm Troubleshooting Guide:
-.P
-https://github\.com/npm/npm/wiki/Troubleshooting#upgrading\-on\-windows
+Many improvements for Windows users have been made in npm 3 \- you will have a better
+experience if you run a recent version of npm\. To upgrade, either use Microsoft's
+upgrade tool \fIhttps://github\.com/felixrieseberg/npm\-windows\-upgrade\fR,
+download a new version of Node \fIhttp://nodejs\.org/download/\fR,
+or follow the Windows upgrade instructions in the
+npm Troubleshooting Guide \fIhttps://github\.com/npm/npm/wiki/Troubleshooting#upgrading\-on\-windows\fR\|\.
.P
If that's not fancy enough for you, then you can fetch the code with
git, and mess with it directly\.