You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems like the publish behaviour is always to add dist-tag latest.
This is the same in real npm-www but there you can override it with publishConfig.
It there anyway to set the npm install --tag to override latest? or at least honor publishConfig as npm-www does.
Original behaviour was to ignore latest tag at all because of the way how npm update worked, but since it was fixed a few months ago, it now makes sense to revert it.
Seems like the publish behaviour is always to add dist-tag latest.
This is the same in real npm-www but there you can override it with publishConfig.
It there anyway to set the
npm install --tag
to override latest? or at least honor publishConfig as npm-www does.See npm/npm#4837
The text was updated successfully, but these errors were encountered: