diff options
| author | isaacs <i@izs.me> | 2019-07-24 23:00:03 -0700 |
|---|---|---|
| committer | Michaël Zasso <targos@protonmail.com> | 2019-08-06 09:05:32 +0200 |
| commit | d7d321b071789f08c65dbb11a0e4b3b6a299af44 (patch) | |
| tree | 1015b8c5da3632fc986b56051a4853ac946c56f4 /deps/npm/man/man1/npm-outdated.1 | |
| parent | 37d27486fce50bd82b6b5095af880d435ed308f8 (diff) | |
| download | android-node-v8-d7d321b071789f08c65dbb11a0e4b3b6a299af44.tar.gz android-node-v8-d7d321b071789f08c65dbb11a0e4b3b6a299af44.tar.bz2 android-node-v8-d7d321b071789f08c65dbb11a0e4b3b6a299af44.zip | |
deps: upgrade npm to 6.10.2
PR-URL: https://github.com/nodejs/node/pull/28853
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
Reviewed-By: Daijiro Wachi <daijiro.wachi@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Yongsheng Zhang <zyszys98@gmail.com>
Diffstat (limited to 'deps/npm/man/man1/npm-outdated.1')
| -rw-r--r-- | deps/npm/man/man1/npm-outdated.1 | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/deps/npm/man/man1/npm-outdated.1 b/deps/npm/man/man1/npm-outdated.1 index 00d28b346e..aee9006752 100644 --- a/deps/npm/man/man1/npm-outdated.1 +++ b/deps/npm/man/man1/npm-outdated.1 @@ -81,9 +81,10 @@ something immutable, like a commit SHA), or it might not, so \fBnpm outdated\fP \fBnpm update\fP have to fetch Git repos to check\. This is why currently doing a reinstall of a Git dependency always forces a new clone and install\. .IP \(bu 2 -\fBis marked as "wanted", but "latest" is\fP\fBbecause npm -uses dist\-tags to manage its\fPlatest\fBand\fPnext\fBrelease channels\.\fPnpm update\fBwill install the _newest_ version, but\fPnpm install npm\fB(with no semver range) -will install whatever's tagged as\fPlatest`\. +\fBnpm@3\.5\.2\fP is marked as "wanted", but "latest" is \fBnpm@3\.5\.1\fP because npm +uses dist\-tags to manage its \fBlatest\fP and \fBnext\fP release channels\. \fBnpm update\fP +will install the \fInewest\fR version, but \fBnpm install npm\fP (with no semver range) +will install whatever's tagged as \fBlatest\fP\|\. .IP \(bu 2 \fBonce\fP is just plain out of date\. Reinstalling \fBnode_modules\fP from scratch or running \fBnpm update\fP will bring it up to spec\. |