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

Two different packages on npm #214

Closed
jhiesey opened this issue Apr 16, 2016 · 8 comments
Closed

Two different packages on npm #214

jhiesey opened this issue Apr 16, 2016 · 8 comments
Labels

Comments

@jhiesey
Copy link

jhiesey commented Apr 16, 2016

I first found https://www.npmjs.com/package/MathJax-node on npm, which appears to be an old version. The current version looks to be https://www.npmjs.com/package/mathjax-node, which differs only by case.

I can't imagine I'm the only one who's downloaded the wrong version. Could you at least publish an update the README on the old one to point people to the new one?

@pkra
Copy link
Contributor

pkra commented Apr 18, 2016

If you install MathJax-node NPM should trigger a deprecation warning that reads:

"npm WARN deprecated [email protected]: WARNING: This project has been renamed to mathjax-node. Install using mathjax-node instead."

We thought that would be sufficient.

Personally, I don't mind one way or another if we add more information somewhere; @dpvc, @zorkow thoughts?

@pkra pkra added the Question label Apr 18, 2016
@dpvc
Copy link
Member

dpvc commented Apr 18, 2016

I suppose changing the README so that the page at https://www.npmjs.com/package/MathJax-node indicates the change would be a reasonable thing to do. Can that be done without screwing up the new package?

@pkra
Copy link
Contributor

pkra commented Apr 18, 2016

I suppose changing the README so that the page at https://www.npmjs.com/package/MathJax-node indicates the change would be a reasonable thing to do.

No objection here.

Can that be done without screwing up the new package?

Yes. We only publish tags (and as long as we don't change the version number in package.json, publishing to npm would fail without damaging the current version on npm).

@pkra
Copy link
Contributor

pkra commented Apr 20, 2016

On second read, I misunderstood you @dpvc. To change the readme on npm we would have to make a new NPM release with the old package name and a new version number in the package.json. That would have to be done manually, I think.

@pkra
Copy link
Contributor

pkra commented Apr 20, 2016

This would be my preferred solution: https://github.com/npm/newww/issues/413

@dpvc
Copy link
Member

dpvc commented Apr 29, 2016

That would have to be done manually, I think.

If we made a branch off the current 0.3.0 tag and changed the README.md and package.json in that branch and then tagged it 0.3.1, would we be able to publish that on npm for MathJax-node without screwing up mathjax-node? If so, I'm OK with doing that.

Waiting for npm to make their changes is also fine with me.

@pkra
Copy link
Contributor

pkra commented May 2, 2016

If we made a branch off the current 0.3.0 tag and changed the README.md and package.json in that branch and then tagged it 0.3.1, would we be able to publish that on npm for MathJax-node without screwing up mathjax-node? If so, I'm OK with doing that.

I don't know but I'm guessing it shouldn't cause any issues. Will do some research.

@pkra
Copy link
Contributor

pkra commented May 3, 2016

Fixed.

@pkra pkra closed this as completed May 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants