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
Publishing a node package under a tag other than the latest is not fully supported. For example, when executing the command npm view with package name (without version) should return a list as it does in default npm registry. Github registry returns blank:
npm view <ORG>/<PACKAGE-NAME>
To replicate, let's say that you have a package.json
name: "@org/test"
version: "1.0.0"
Which is published under a hypothetical tag "custom"
npm publish --access=restricted --tag=custom
The UI will show "latest".
If you try to declare a tag via dist-tags command you'd get the warning "custom" tag already set
npm WARN dist-tag add custom is already set to version 1.0.0
Which can be verified and confirmed if
npm info @org/test@1.0.0
dist-tags:
custom: 1.0.0
Thus, the command dist-tags by package name is expected to return the list of tags as npm does:
npm view @org/test dist-tags
This returns blank. However if the version appended to the package name is specified a list of tags is returned
BugSomething isn't working correctlyPackagesHost your dependencies, libraries, and production-ready code, right from your repository
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Select Topic Area
Bug
Body
Publishing a node package under a tag other than the latest is not fully supported. For example, when executing the command npm view with package name (without version) should return a list as it does in default npm registry. Github registry returns blank:
To replicate, let's say that you have a package.json
Which is published under a hypothetical tag "custom"
The UI will show "latest".
If you try to declare a tag via dist-tags command you'd get the warning "custom" tag already set
Which can be verified and confirmed if
Thus, the command dist-tags by package name is expected to return the list of tags as npm does:
This returns blank. However if the version appended to the package name is specified a list of tags is returned
{ custom: '1.0.0' }
Beta Was this translation helpful? Give feedback.
All reactions