1 .TH "NPM\-TAG" "1" "October 2016" "" ""
3 \fBnpm-tag\fR \- Tag a published version
8 npm tag <name>@<version> [<tag>]
13 THIS COMMAND IS DEPRECATED\. See npm help dist\-tag for details\.
15 Tags the specified version of the package with the specified tag, or the
16 \fB\-\-tag\fP config if not specified\.
18 A tag can be used when installing packages as a reference to a version instead
19 of using a specific version number:
23 npm install <name>@<tag>
27 When installing dependencies, a preferred tagged version may be specified:
31 npm install \-\-tag <tag>
35 This also applies to \fBnpm dedupe\fP\|\.
37 Publishing a package always sets the "latest" tag to the published version\.
40 Tags can be used to provide an alias instead of version numbers\. For
41 example, \fBnpm\fP currently uses the tag "next" to identify the upcoming
42 version, and the tag "latest" to identify the current version\.
44 A project might choose to have multiple streams of development, e\.g\.,
48 Tags must share a namespace with version numbers, because they are
49 specified in the same slot: \fBnpm install <pkg>@<version>\fP vs \fBnpm
50 install <pkg>@<tag>\fP\|\.
52 Tags that can be interpreted as valid semver ranges will be
53 rejected\. For example, \fBv1\.4\fP cannot be used as a tag, because it is
54 interpreted by semver as \fB>=1\.4\.0 <1\.5\.0\fP\|\. See
55 https://github\.com/npm/npm/issues/6082\|\.
57 The simplest way to avoid semver problems with tags is to use tags
58 that do not begin with a number or the letter \fBv\fP\|\.