Stay organized with collections
Save and categorize content based on your preferences.
Learn about troubleshooting steps that you might find helpful if you run into
problems managing Node.js packages in Artifact Registry.
Can't overwrite an existing version of a package
You can only publish a specific version of a package once.
This is an npm restriction
to ensure that the contents of a published package version are always the same,
and to prevent tampering with dependencies.
As a result, you cannot:
Overwrite a package version by publishing it again to the repository
Remove a package or its version from the repository, and then publish
a package with the same name and version number
Tags can help you streamline installation of packages at a
specific stage of development. For information about working with tags when you
publish and install package, see Managing Node.js packages.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["You can only publish a specific version of a Node.js package once due to npm restrictions."],["Overwriting an existing package version by republishing it is not allowed."],["Removing a package and then publishing a new one with the same name and version number is also not allowed."],["Tags can assist with managing the installation of packages at different development stages."]]],[]]
