Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish with version number which is previously published overrides previous version #19

Open
trygve-lie opened this issue Sep 10, 2013 · 5 comments

Comments

@trygve-lie
Copy link

NPM will complain if one try to publish an package with the same version number as a previously published package:

Example:

npm ERR! publish fail Cannot publish over existing version.
npm ERR! publish fail Update the 'version' field in package.json and try again.

Reggie silently publishes the package and overrides the old version. In my humble opinion I think Reggie should follow NPM on this. Its very easy to forget to up a version number when publishing and if its forgotten its good that the registry complains.

If this is a wanted feature I can take a stab at it and make a pull request.

@bajtos
Copy link
Collaborator

bajtos commented Sep 12, 2013

Thanks for reporting the issue.

I think Reggie should follow NPM on this.

Absolutely. See also #5.

If this is a wanted feature I can take a stab at it and make a pull request.

Excellent, go for it!

@paolodm
Copy link
Contributor

paolodm commented Sep 23, 2013

Just curious what NPM would do in this scenario? Would it override?

@trygve-lie
Copy link
Author

@paolodm NPM will prompt the user with an error message saying that the version already exist. NPM does then not override.

@Bobris
Copy link

Bobris commented Oct 2, 2015

This is source of many mistakes, it would be really good to have this implemented ... 👍

@bajtos
Copy link
Collaborator

bajtos commented Oct 2, 2015

@Bobris we don't have enough time to maintain Reggie. My recommendation is to use sinopia, I believe it does not allow you to re-publish the same version.

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

No branches or pull requests

4 participants