This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
npm version
does allow to set versions smaller than the current version
#4087
Comments
seriousManual
added a commit
to seriousManual/npm
that referenced
this issue
Nov 5, 2013
referencing npm#4087 if the version is smaller or equals an error is thrown, can be overwritten be --force
It's a half measure, writing 10.0.1 instead of 1.0.1 is as undesirable as 0.0.1 really. You should probably use |
i agree. |
This really doesn't protect you from anything. |
@zaphod1984 can you please close this in favour of your pull request? FYI a handy way to convert an issue to a PR (at least on osx) is using hub |
will do, thanks for the heads up. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
its easy to accidently write
npm version 0.0.1
instead ofnpm version 1.0.1
.maybe outputting a warning to the user or demanding the usage of a force parameter to actually set a lower version would by sufficient.
The text was updated successfully, but these errors were encountered: