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.18
1 files changed, 4 insertions, 4 deletions
diff --git a/deps/npm/man/man1/npm-README.1 b/deps/npm/man/man1/npm-README.1
index b7c50819f8..1af9c6a0bd 100644
--- a/deps/npm/man/man1/npm-README.1
+++ b/deps/npm/man/man1/npm-README.1
@@ -1,4 +1,4 @@
-.TH "NPM" "1" "January 2017" "" ""
+.TH "NPM" "1" "February 2017" "" ""
.SH "NAME"
\fBnpm\fR \- a JavaScript package manager
.P
@@ -10,9 +10,9 @@ This is just enough info to get you up and running\.
Much more info available via \fBnpm help\fP once it's installed\.
.SH IMPORTANT
.P
-\fBYou need node v0\.10 or higher to run this program\.\fR
+\fBYou need node v4 or higher to run this program\.\fR
.P
-To install an old \fBand unsupported\fR version of npm that works on node 0\.3
+To install an old \fBand unsupported\fR version of npm that works on node v0\.12
and prior, clone the git repo and dig through the old tags and branches\.
.P
\fBnpm is configured to use npm, Inc\.'s public package registry at
@@ -83,7 +83,7 @@ for testing, or running stuff without actually installing npm itself\.)
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,
+download a new version of Node \fIhttps://nodejs\.org/en/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