This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
npm-dist-tag docs: Explain why the latest tag matters
#10787
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Explain why one would care about the `latest` tag, by explaining its special significance to `npm install`. Currently, only its default status with respect to `npm publish` is mentioned. * Also, avoid using npm as a meta-example, as this causes confusion between npm-the-tool and npm-the-project. The old docs made it sound like the `next` tag might've has special significance to npm-the-tool, when it was instead talking about npm-the-project (AFAIK). * Mention common practice regarding tagging unstable releases, as this is not universally known. * Include the term "prerelease" for SEO's sake
iarna
pushed a commit
that referenced
this pull request
Dec 18, 2015
* Explain why one would care about the `latest` tag, by explaining its special significance to `npm install`. Currently, only its default status with respect to `npm publish` is mentioned. * Also, avoid using npm as a meta-example, as this causes confusion between npm-the-tool and npm-the-project. The old docs made it sound like the `next` tag might've has special significance to npm-the-tool, when it was instead talking about npm-the-project (AFAIK). * Mention common practice regarding tagging unstable releases, as this is not universally known. * Include the term "prerelease" for SEO's sake PR-URL: #10787 Credit: @cvrebert
iarna
pushed a commit
that referenced
this pull request
Jan 7, 2016
* Explain why one would care about the `latest` tag, by explaining its special significance to `npm install`. Currently, only its default status with respect to `npm publish` is mentioned. * Also, avoid using npm as a meta-example, as this causes confusion between npm-the-tool and npm-the-project. The old docs made it sound like the `next` tag might've has special significance to npm-the-tool, when it was instead talking about npm-the-project (AFAIK). * Mention common practice regarding tagging unstable releases, as this is not universally known. * Include the term "prerelease" for SEO's sake PR-URL: #10787 Credit: @cvrebert
|
This landed in v3.5.4 and is still awaiting merge to LTS. |
zkat
pushed a commit
that referenced
this pull request
Jan 19, 2016
* Explain why one would care about the `latest` tag, by explaining its special significance to `npm install`. Currently, only its default status with respect to `npm publish` is mentioned. * Also, avoid using npm as a meta-example, as this causes confusion between npm-the-tool and npm-the-project. The old docs made it sound like the `next` tag might've has special significance to npm-the-tool, when it was instead talking about npm-the-project * Mention common practice regarding tagging unstable releases, as this is not universally known. * Include the term "prerelease" for SEO's sake PR-URL: #10787 Credit: @cvrebert
|
This landed in 2.14.16 =) |
This was referenced Jan 31, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
latesttag, by explaining its special significance tonpm install. Currently, only its default status with respect tonpm publishis mentioned.nexttag might've has special significance to npm-the-tool, when it was instead talking about npm-the-project (AFAIK).Refs twbs/bootstrap#18520