You cannot publish over the previously published versions

Question

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?

score 21 · Answer 1 · answered Oct 31 '19 at 17:44

21

This helped me:

Open Command Prompt and do the following steps.

npm version <new_Version_No>
npm publish

answered Oct 31 '19 at 17:44

Adrita Sharma

19,704
10
55
71

Is there a way to enhance my `package.json` in such a way that it always installs the latest version available on npm for a particular dependency ? something like `"black-duck-lib": "_latest_",`. I dont want to open a separate question for this small thing. plz help. – Tanzeel Oct 26 '21 at 18:24

score 9 · Answer 2 · answered Dec 23 '18 at 04:06

9

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.

answered Dec 23 '18 at 04:06

MarvinJWendt

1,871
7
29

Iceberg · Answer 3 · 2021-10-06T07:07:39.913

9

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`
},

edited Oct 06 '21 at 07:07

answered Jul 13 '20 at 07:06

Iceberg

1,860
15
16

After spending hours trying many solutions. This answer solved the issue. Thanks – eakl Feb 09 '22 at 23:25

score 4 · Answer 4 · answered Nov 19 '19 at 11:23

4

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.

answered Nov 19 '19 at 11:23

Mukul Anand

507
2
19

score 1 · Answer 5 · answered Dec 21 '18 at 15:45

1

You can try the following:

Update npm version to latest.
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.

answered Dec 21 '18 at 15:45

Gaurang Tandon

6,110
10
44
79

score 1 · Answer 6 · answered Sep 23 '19 at 20:07

1

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.

answered Sep 23 '19 at 20:07

yegor256

97,508
114
426
573

score 1 · Answer 7 · answered Apr 19 '21 at 14:58

1

It happens when there is already npm module with same version.

We need to increment the npm module version and publish it again.

answered Apr 19 '21 at 14:58

Yuvraj Patil

6,242
3
46
50

You cannot publish over the previously published versions

7 Answers7