docs(npm-install): clarify --tag does not override package.json #8801
+2
−0
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.
Description
This PR clarifies that the
--tagoption fornpm installonly applies to packages specified on the command line, and does not override version ranges inpackage.json.Changes
--tagdoes not affect dependencies listed inpackage.jsonpackage.jsontake precedence over the--tagflagnpm install foo@betaContext
Users were confused when
npm install --tag betadidn't install beta-tagged versions of dependencies listed inpackage.json. The issue reporter discovered that whenpackage.jsonspecifies a version range like"^0.3.0", the--tagflag is ignored and npm installs a version matching the range, even if thebetatag points to a different version (like0.4.0-beta.1). This was marked as needing better documentation/logging to make the behavior less surprising.Closes #4685