Reputation: 2160
I've updated my package using npm version minor
to go from 0.4.0 to 0.5.0, and both package.json
and package-lock.json
reflect this. However when I run the npm publish
command it says:
You cannot publish over the previously published versions: 0.4.0
Is there another place I need to update the semver in order to publish?
Upvotes: 37
Views: 45709
Reputation: 97
As other mentioned just You already publish this version! so increment that version for example if it (1.1.1) change it to(1.1.2) then npm i
Upvotes: 0
Reputation: 3352
In your package.json, there might exist a publish
script command with content of npm publish ...
, remove or rename the publish
command in your scripts of package.json if there is one.
Take the following code for example, this scripts.publish
command will again be triggered by npm publish --access public
, running recursively.
"scripts": {
"publish": "npm publish --access public" // this was being triggered by running `npm publish`
},
Upvotes: 16
Reputation: 8736
It happens when there is already npm module with same version.
We need to increment the npm module version and publish it again.
Upvotes: 4
Reputation: 626
npm version [patch|minor|major|<version_no>]
should be done to bump up the version and then
npm publish
for public visibility add --access public
This should do it.
Upvotes: 5
Reputation: 22213
This helped me:
Open Command Prompt and do the following steps.
npm version <new_Version_No>
npm publish
Upvotes: 32
Reputation: 105083
For some reason I was getting this error when I was trying to increase my version from 0.0.0
to 0.0.1
. However, updating from 0.0.0
to 0.1.0
worked just fine.
Upvotes: 4
Reputation: 2684
take a look at your package.json
.
Is the version
actually set to 0.5.0
?
If not consider setting it manually there. NPM is telling you that you already have a version 0.4.0
and it cannot publish it again. So it seems to think that it's still on 0.4.0
.
Upvotes: 12
Reputation: 6753
You can try the following:
cd
into the parent folder (of the folder containing package.json
i.e. cd
into A
if your files are A/B/package.json
) and then run the command npm publish B
.Doing both fixed the issue for me.
Upvotes: 1