Design Converter
- Technologies
Flutter
React
Shopify
Flutter
React
Shopify
- Resource
Discord
Discord
Design Converter
Flutter
React
Shopify
Flutter
React
Shopify
Discord
Discord
Education
Last updated on Mar 12, 2025
•4 mins read
Last updated on Mar 12, 2025
•4 mins read
How does the npm publish tag work?
Managing package versions in npm can get tricky without understanding how the npm publish tag works. It helps control which package version gets installed by default and allows developers to test specific versions.
This blog breaks down npm publish tags, including dist tags, npm versioning, and how npm install handles them.
The npm publish tag command helps assign specific dist tags to published versions of an npm package. By default, npm publish assigns the latest tag to a new package version. However, when working with multiple versions, such as stable releases and pre-releases (e.g., beta), managing tags becomes essential.
• Control which version users get when they run npm install without specifying a version number.
• Maintain different release channels (e.g., stable, beta, or experimental versions).
• Ensure production stability by preventing premature adoption of an unstable release.
Each npm package version can have one or more dist tags. The latest tag is applied by default, but other tags can be assigned to manage releases.
When you run npm publish, the latest tag is assigned unless specified otherwise:
1npm publish
This assigns the latest dist tag to the newly published version.
To publish a beta version without overriding the stable release, use:
1npm publish --tag beta
This assigns the beta tag to the package instead of latest.
NPM provides several commands to view, add, or remove dist tags.
To see all dist tags for a published package:
1npm dist-tag ls <package-name>
For example:
1npm dist-tag ls my-package
If you have already published a package and want to add a specific dist tag:
1npm dist-tag add my-package@1.2.3 beta
This means version 1.2.3 can now be installed using:
1npm install my-package@beta
To delete a dist tag:
1npm dist-tag rm my-package beta
This does not delete the package version—only the beta tag is removed.
When installing an npm package, the tag determines which version is retrieved.
1npm install my-package
This fetches the version with the latest dist tag.
1npm install my-package@1.2.3
This fetches version 1.2.3, regardless of tags.
To install a beta version:
1npm install my-package@beta
This retrieves the version currently assigned to the beta tag.
When a package is updated, the latest dist tag moves to the newest version. However, specific dist tags such as beta or rc (release candidate) remain on their assigned versions.
1npm publish --tag latest
1npm publish --tag beta
1npm dist-tag add my-package@2.0.0-beta.2 beta
Using dist tags effectively ensures that test users get beta versions while production users remain on stable releases.
In CI/CD pipelines, automated publishing ensures smooth releases. A typical script might look like this:
1if [[ "$BRANCH_NAME" == "main" ]]; then 2 npm version patch 3 npm publish --tag latest 4elif [[ "$BRANCH_NAME" == "beta" ]]; then 5 npm version prerelease --preid=beta 6 npm publish --tag beta 7fi
This script:
• Publishes stable releases with the latest tag from main.
• Publishes pre-releases with the beta tag from the beta branch.
Issue: latest Tag Points to an Old Version
Solution: Manually Update the latest tag
1npm dist-tag add my-package@2.0.0 latest
Issue: npm install Installs the Wrong Version
Solution: Check Assigned dist tags
1npm dist-tag ls my-package
If necessary, reassign tags accordingly.
Issue: Running npm publish Overwrites latest by Default
Solution: Use Explicit Tags
Always specify --tag when publishing non-stable versions:
1npm publish --tag beta
• npm publish tag allows fine control over package versions.
• dist tags determine which version is installed by default.
• npm install fetches versions based on dist tags assignments.
• Using npm publish tag beta ensures test releases do not override stable ones.
• Automating tagging in CI/CD pipelines streamlines the release process.
Understanding the npm publish tag helps keep package releases predictable and organized. It simplifies managing beta versions and updating new releases. By using dist tags effectively, developers can maintain a smooth and controlled development process.
Tired of manually designing screens, coding on weekends, and technical debt? Let DhiWise handle it for you!
You can build an e-commerce store, healthcare app, portfolio, blogging website, social media or admin panel right away. Use our library of 40+ pre-built free templates to create your first application using DhiWise.
