X-Git-Url: https://gerrit.simantics.org/r/gitweb?a=blobdiff_plain;ds=inline;f=org.simantics.maps.server%2Fnode%2Fnode-v4.8.0-win-x64%2Fnode_modules%2Fnpm%2Fhtml%2Fdoc%2Fcli%2Fnpm-tag.html;fp=org.simantics.maps.server%2Fnode%2Fnode-v4.8.0-win-x64%2Fnode_modules%2Fnpm%2Fhtml%2Fdoc%2Fcli%2Fnpm-tag.html;h=e8ec4eccdc2212289689824ab2dc2ab0ad1f61c8;hb=2529be6d456deeb07c128603ce4971f1dc29b695;hp=0000000000000000000000000000000000000000;hpb=2636fc31c16c23711cf2b06a4ae8537bba9c1d35;p=simantics%2Fdistrict.git diff --git a/org.simantics.maps.server/node/node-v4.8.0-win-x64/node_modules/npm/html/doc/cli/npm-tag.html b/org.simantics.maps.server/node/node-v4.8.0-win-x64/node_modules/npm/html/doc/cli/npm-tag.html new file mode 100644 index 00000000..e8ec4ecc --- /dev/null +++ b/org.simantics.maps.server/node/node-v4.8.0-win-x64/node_modules/npm/html/doc/cli/npm-tag.html @@ -0,0 +1,66 @@ + + +
Tag a published version
+npm tag <name>@<version> [<tag>]
+
THIS COMMAND IS DEPRECATED. See npm-dist-tag(1) for details.
+Tags the specified version of the package with the specified tag, or the
+--tag
config if not specified.
A tag can be used when installing packages as a reference to a version instead +of using a specific version number:
+npm install <name>@<tag>
+
When installing dependencies, a preferred tagged version may be specified:
+npm install --tag <tag>
+
This also applies to npm dedupe
.
Publishing a package always sets the "latest" tag to the published version.
+Tags can be used to provide an alias instead of version numbers. For
+example, npm
currently uses the tag "next" to identify the upcoming
+version, and the tag "latest" to identify the current version.
A project might choose to have multiple streams of development, e.g., +"stable", "canary".
+Tags must share a namespace with version numbers, because they are
+specified in the same slot: npm install <pkg>@<version>
vs npm
+install <pkg>@<tag>
.
Tags that can be interpreted as valid semver ranges will be
+rejected. For example, v1.4
cannot be used as a tag, because it is
+interpreted by semver as >=1.4.0 <1.5.0
. See
+https://github.com/npm/npm/issues/6082.
The simplest way to avoid semver problems with tags is to use tags
+that do not begin with a number or the letter v
.