-
Notifications
You must be signed in to change notification settings - Fork 332
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
Setup npm package #138
Setup npm package #138
Conversation
Hi @bartvanandel. Yes, we can add it to master. I personally don't use npm regularly , so it's better somebody else handles it. If you like, I can add you as the maintainer of this part. |
@adam-waldenberg, that sounds fine to me. Note that I may have to update the package version number if a new npm release is required, at least in package.json. I'll try to keep those changes to a minimum. |
Any news about this pull request? |
Hi @bartvanandel . Will get to it as soon as I get time. In the future, I'll make sure to modify package.json when a new version is branhced. I'm planing a 0.4.5 release next. I'll let you handle the publishing when new versions get released. |
Okay, thanks, please inform me when the time is ripe. |
Changed a few things a few minutes ago.
|
@bartvanandel Officially merged in master. I'll let you know when I have 0.4.5 ready. I'm planning to have it ready for release relatively soon. |
I've put some effort into turning this nice tool into an npm package. I've just published and tested it, works like a charm! Would you consider pulling the changes into master?
NB: I've added myself as a contributor for this, but I've set up the package to point to the original (your) github page, assuming you'd agree. If this is not desired, please let me know and I'll change it. If you'd like to be able to push to npm yourself, let me know as well so I can set this up.