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

Release as npm module #15

Open
ryanblock opened this issue May 7, 2020 · 1 comment
Open

Release as npm module #15

ryanblock opened this issue May 7, 2020 · 1 comment

Comments

@ryanblock
Copy link

<3

Happy to lend a hand if you like. Would make consuming this dataset – especially versioning! – much easier in Node.js environments.

@hyperknot
Copy link
Owner

hyperknot commented May 7, 2020

I was thinking about it a lot.

Advantages:

  • npm upgrade works without looking up releases in GitHub

Disadvantages:

  • Why is NPM special, over PIP or Ruby gems or some other package manager? If we release on NPM we should release on PIP as well.
  • These are JSON files, not related to any particular programming language.
  • Needs to be 4 packages, not 1. For NPM and PIP it'd be 8 packages in total.
  • NPM has problems with uploading big releases. Stackoverflow has some hacks using curl.
  • Need to write a versioning + release implementation.
  • Need to maintain all those 8 packages in npm and pip.

All in all, I concluded that it's not worth the effort just to avoid looking up the version number in GitHub.

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

2 participants