Npm ERR! Invalid version on npm install

Question

Whenever I run npm install I get

npm ERR! Invalid Version:

This is the log file.

43 verbose stack TypeError: Invalid Version: 43 verbose stack at new SemVer (C:\Users\Myself\AppData\Roaming\npm\node_modules\npm\node_modules\semver\classes\semver.js:38:13) 43 verbose stack at compare (C:\Users\Myself\AppData\Roaming\npm\node_modules\npm\node_modules\semver\functions\compare.js:3:32) 43 verbose stack at Object.gte (C:\Users\Myself\AppData\Roaming\npm\node_modules\npm\node_modules\semver\functions\gte.js:2:30) 43 verbose stack at Node.canDedupe (C:\Users\Myself\AppData\Roaming\npm\node_modules\npm\node_modules\@npmcli\arborist\lib\node.js:1054:32) 43 verbose stack at PlaceDep.pruneDedupable (C:\Users\Myself\AppData\Roaming\npm\node_modules\npm\node_modules\@npmcli\arborist\lib\place-dep.js:465:14) 43 verbose stack at PlaceDep.placeInTree (C:\Users\Myself\AppData\Roaming\npm\node_modules\npm\node_modules\@npmcli\arborist\lib\place-dep.js:326:14) 43 verbose stack at PlaceDep.place (C:\Users\Myself\AppData\Roaming\npm\node_modules\npm\node_modules\@npmcli\arborist\lib\place-dep.js:214:10) 43 verbose stack at new PlaceDep (C:\Users\Myself\AppData\Roaming\npm\node_modules\npm\node_modules\@npmcli\arborist\lib\place-dep.js:71:10) 43 verbose stack at C:\Users\Myself\AppData\Roaming\npm\node_modules\npm\node_modules\@npmcli\arborist\lib\arborist\build-ideal-tree.js:965:31 43 verbose stack at Array.map (<anonymous>) 44 verbose cwd C:\Users\Dont\Want\To\Reveal\This\Information 45 verbose Windows_NT 10.0.19042 46 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Myself\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "i" "-force" 47 verbose node v16.14.0 48 verbose npm v8.5.1 49 error Invalid Version: 50 verbose exit 1 51 timing npm Completed in 18500ms

I don't understand what version of what is invalid? Help!

It would help if you would provide your package.json. Either the whole file – or at least "version": "x.x.x" and everything under "dependencies". — Henke
– Henke, Commented Apr 20, 2022 at 14:08

Victor Karangwa · Accepted Answer · 2022-06-20 15:07:36Z

53

Deletingnode_modules and package-lock.json (OR yarn.lock) solved the issue for me.

answered Jun 20, 2022 at 15:07

Victor Karangwa

2,26622 silver badges19 bronze badges

Sign up to request clarification or add additional context in comments.

7 Comments

Pavel 'Strajk' Dolecek Over a year ago

thx! Sometimes you just wanna make it work without digging deeper and trying to understand all the nuances about npm.

nisanarz Over a year ago

thanks, just deleting the package.lock worked for me.

Raphael Pinel Over a year ago

OK, it works to delete the package-lock.json, the question is why? How to know where the error comes from? I am getting error Invalid Version: ^5.0.0 in an Angular 13 app. But why? Which package? I don't see it in the logs. Must be this in package.json: "resolutions": { "webpack": "^5.0.0" }

Martin Torp Over a year ago

If you don't want to delete your lock file: Open the lock file, and delete all occurrences of the package npm complains about. Save the lock file and run npm install again.

Leffa Over a year ago

rm -f node_modules rm package-lock.json npm cache clean --force

|

jbuhacoff · Accepted Answer · 2022-12-11 14:44:51Z

Delete package-lock.json and node_modules/.package-lock.json, then run the npm install command again.

This solves the problem for me without having to delete and re-download all the modules that were installed correctly.

This actually solved my problem. I didn't have to delete the whole node_modules folder

Abraham · Accepted Answer · 2024-08-31 08:32:27Z

7

Solution

Delete the node_modules folder, remove package.lock and clean cache:

rm -rf node_modules/ npm cache clean

If still not working, you want to take the risk of breaking changes, this will do it

rm package-lock.json npm cache clean --force

Re-install

npm install

or simply

npm i

edited Aug 31, 2024 at 8:32

answered Aug 10, 2022 at 20:41

Abraham

16.3k12 gold badges91 silver badges124 bronze badges

3 Comments

Robin Bastiaan Over a year ago

I would like to ask why this works.

Leffa Over a year ago

rm -f node_modules rm package-lock.json npm cache clean --force

astroanu Over a year ago

deleting the lock file is not recommended, you may unintentionally break something

Maxime Chéramy · Accepted Answer · 2022-06-09 15:20:45Z

2

I had the same error with [email protected]. Fixed by downgrading to [email protected].

answered Jun 9, 2022 at 15:20

Maxime Chéramy

19k10 gold badges58 silver badges77 bronze badges

2 Comments

Saeed Hemmati Over a year ago

Actually you upgraded the npm version not downgrade it.

Maxime Chéramy Over a year ago

@SaeedHemmati 8.5 is lower than 8.12.

bitbuoy · Accepted Answer · 2022-04-05 08:14:59Z

Solution : if you check your "package.json" file in your projects root, it's probably missing one or all of the following properties:

name
version

for version, it has to be in the form "x.x.x", i.e in my(and probably yours) case "1.0.0"

for name you can obtain it from the "app.json" for example in my case:

{ "expo": { "name": "the-10-min", "slug": "the-10-min", "privacy": "public", "platforms": [ "ios", "android", "web" ],

so in my case the name property in the "package.json" file will be "the-10-min" .Plug in the values for name and version then run the command "npm install"

Basit Balogun · Accepted Answer · 2022-08-28 05:26:27Z

You should also ensure that the name properties in app.json and package.json are the same- they were different in mine and caused the error

shai tibber · Accepted Answer · 2023-02-08 15:38:15Z

Ran into a similar problem after cloning an old project. Tried all of these solutions, none worked. Turns out my problem was due to deprecated package versions. I removed them all and added them gradually until I figured out which were the ones giving me problems. Luckily, The newer versions of these packages were ok.

Yaya HC · Accepted Answer · 2023-12-19 12:12:49Z

Try to remove the "version" key from your package.json file.

For example, your package.json may look like this:

{ "name": "app_name", "version": "1.0.0", "private": true, // rest of file }

Remove the "version" line so it becomes:

{ "name": "app_name", "private": true, // rest of file }

Removing the version number forces npm to use the latest available version of each dependency instead of trying to install a specific one. This can resolve errors where npm tries to install an invalid or unavailable version.

Let me know if the error persists after removing the version number, as there could be other causes. But this solution works for me.

Thank you for the feedback and tips on improving my answer! I have updated my answer to follow the formatting guidelines better and provide more clarity. Please see the revised version @Yunnosch

Collectives™ on Stack Overflow

Npm ERR! Invalid version on npm install

8 Answers 8

7 Comments

1 Comment

Solution

3 Comments

2 Comments

Comments

Comments

Comments

3 Comments

Hot Network Questions

Collectives™ on Stack Overflow

8 Answers 8

7 Comments

1 Comment

Solution

3 Comments

2 Comments

Comments

Comments

Comments

3 Comments

Related