-
Notifications
You must be signed in to change notification settings - Fork 98
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
Comments
If you install "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? |
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? |
No objection here.
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). |
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. |
This would be my preferred solution: https://github.com/npm/newww/issues/413 |
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. |
I don't know but I'm guessing it shouldn't cause any issues. Will do some research. |
Fixed. |
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?
The text was updated successfully, but these errors were encountered: