Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

Invalid Version 1.0.2beta #12004

Closed
craigodavis opened this issue Mar 22, 2016 · 6 comments
Closed

Invalid Version 1.0.2beta #12004

craigodavis opened this issue Mar 22, 2016 · 6 comments

Comments

@craigodavis
Copy link

Hi, I just installed npm 3.8.2 and am getting the following error when running npm install:
npm ERR! Darwin 15.3.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v5.9.0
npm ERR! npm v3.8.2

npm ERR! Invalid Version: 1.0.2beta
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues

Here is the log file:
npm-debug.log.zip

Any help would be greatly appreciated!

@zkat
Copy link
Contributor

zkat commented Mar 24, 2016

Are you using 1.0.2beta as the version for your package? That's not a valid semver range. According to the semver spec, the correct syntax would be 1.0.2-beta in order to be valid.

@godserahul1986
Copy link

@zkat So the semver specs are applied on all npm versions now onwards? I had a package versioned 9.2.0.2 and everything worked fine weeks back and now the build fails with the error Invalid version: 9.2.0.2

@zkat
Copy link
Contributor

zkat commented Apr 19, 2016

@godserahul1986 I honestly don't know what version of npm would allow you to get away with an invalid semver like that -- version was never meant to be anything but valid semver ranges, and any case where that was possible is simply a bug.

@computnik
Copy link

I tried with npm v3.8.6, the issue is still there.. Is there an expected timeline when this would get fixed?

@kenany
Copy link
Contributor

kenany commented May 3, 2016

@nikhilmotiani There's no bug here as far as I can tell.

@npm-robot
Copy link

We're closing this support issue as it has gone three days without activity. The npm CLI team itself does not provide support via this issue tracker, but we are happy when users help each other here. In our experience once a support issue goes dormant it's unlikely to get further activity. If you're still having problems, you may be better served by joining package.community and asking your question there.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants