summaryrefslogtreecommitdiff
path: root/deps/npm/man/man1/npm-tag.1
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/man/man1/npm-tag.1')
-rw-r--r--deps/npm/man/man1/npm-tag.180
1 files changed, 0 insertions, 80 deletions
diff --git a/deps/npm/man/man1/npm-tag.1 b/deps/npm/man/man1/npm-tag.1
deleted file mode 100644
index ac9450d1b7..0000000000
--- a/deps/npm/man/man1/npm-tag.1
+++ /dev/null
@@ -1,80 +0,0 @@
-.TH "NPM\-TAG" "1" "November 2016" "" ""
-.SH "NAME"
-\fBnpm-tag\fR \- Tag a published version
-.SH SYNOPSIS
-.P
-.RS 2
-.nf
-[DEPRECATED] npm tag <name>@<version> [<tag>]
-See `dist\-tag`
-.fi
-.RE
-.SH DESCRIPTION
-.P
-THIS COMMAND IS DEPRECATED\. See npm help dist\-tag for details\.
-.P
-Tags the specified version of the package with the specified tag, or the
-\fB\-\-tag\fP config if not specified\.
-.P
-A tag can be used when installing packages as a reference to a version instead
-of using a specific version number:
-.P
-.RS 2
-.nf
-npm install <name>@<tag>
-.fi
-.RE
-.P
-When installing dependencies, a preferred tagged version may be specified:
-.P
-.RS 2
-.nf
-npm install \-\-tag <tag>
-.fi
-.RE
-.P
-This also applies to \fBnpm dedupe\fP\|\.
-.P
-Publishing a package always sets the "latest" tag to the published version\.
-.SH PURPOSE
-.P
-Tags can be used to provide an alias instead of version numbers\. For
-example, \fBnpm\fP currently uses the tag "next" to identify the upcoming
-version, and the tag "latest" to identify the current version\.
-.P
-A project might choose to have multiple streams of development, e\.g\.,
-"stable", "canary"\.
-.SH CAVEATS
-.P
-Tags must share a namespace with version numbers, because they are
-specified in the same slot: \fBnpm install <pkg>@<version>\fP vs \fBnpm
-install <pkg>@<tag>\fP\|\.
-.P
-Tags that can be interpreted as valid semver ranges will be
-rejected\. For example, \fBv1\.4\fP cannot be used as a tag, because it is
-interpreted by semver as \fB>=1\.4\.0 <1\.5\.0\fP\|\. See
-https://github\.com/npm/npm/issues/6082\|\.
-.P
-The simplest way to avoid semver problems with tags is to use tags
-that do not begin with a number or the letter \fBv\fP\|\.
-.SH SEE ALSO
-.RS 0
-.IP \(bu 2
-npm help publish
-.IP \(bu 2
-npm help install
-.IP \(bu 2
-npm help dedupe
-.IP \(bu 2
-npm help 7 registry
-.IP \(bu 2
-npm help config
-.IP \(bu 2
-npm help 7 config
-.IP \(bu 2
-npm help dist\-tag
-.IP \(bu 2
-npm help 5 npmrc
-
-.RE
-