Error Command Failed Npm Version

Posted on  by admin


Modified1 year, 5 months ago.

I am trying to patch a version of my Angular project using the command - npm version patch but getting an error - . The same command used to work fine earlier and suddenly stopped npm version is 6.4.0.

11 gold badge99 silver badges2727 bronze badges. 2727 bronze badges. I was able to resolve the error by myself.

The error was that the patch version was written as 01.i.e.

2018.11.01 instead of 2018.11.1. npm version patch failed without an explanatory message.

11 gold badge99 silver badges2727 bronze badges.

2727 bronze badges. Yes, you're correct the semver version number must be a valid integer from [0-9] inclusively.

For reference, npm uses node-semver as their semver parser to deal with versioning on their end.

Also, you mentioned the error failed silently, you need to run your command with the verbose flag to see everything.

For example, if you do a npm version patch --verbose, npm would spit out additional information for why the command failed.

You can use the verbose flag on any valid npm command.

Hopefully that helps! 44 gold badges2323 silver badges4646 bronze badges.

4646 bronze badges. I ran into the same issue with npm v6.14.8 and eventually discovered that I'd forgotten to include the "version" property in my package.json at all!

This now works in npm 7.0.9 and later, but the change hasn't been backported to v6, so be sure you haven't left it out if you're still using that.

2727 gold badges126126 silver badges151151 bronze badges.

151151 bronze badges. Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.