-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Take over official snappy package on npm #16
Comments
Oh it's very coooooooool!!
Yes. after this I will write a migration guite in |
@kesla Hey I've opened a pull request here to finish the package rename job: https://github.com/Brooooooklyn/snappy/pull/new/snappy-7 Feel free to review and leave some comments on it! |
Very cool, the PR's looking good. I added you as a maintainer to snappy on npm. I'll deprecate my repo once you've published this as version 7 on npm! |
I saw that you did a release of snappy 7, coming from this repo. Very cool! |
Yes,thanks again! |
Doe to this change, something went wrong and this library does not work well with mongodb nodejs driver now in v7.0. |
@adityapatadia I will take a look soon |
@adityapatadia it might, as library API has slightly changed and ie. |
See https://github.com/Brooooooklyn/snappy/releases/tag/v7.0.2, |
Hi , any chance you can point me to that migration guide for people using the old API? |
Hi!
Are you interested in taking over the snappy-package on npm?
snappy
is the first serious npm module I ever published, so I gotta be honest that it'll be a bit difficult to let it go, but since this project is snappier than mine, I think it would make sense.My suggestion would be that I add you as a maintainer to the snappy package and that you publish a new version of it (as version 7.0.0 so that no existing installations of snappy are affected).
I would than also deprecate my repo on github, sending them your way instead.
Let me know what you think about my suggestion, I think it would be a cool thing to do.
The text was updated successfully, but these errors were encountered: