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

Please publish a new version of this module #13

Open
maxmil7 opened this issue Oct 28, 2020 · 10 comments
Open

Please publish a new version of this module #13

maxmil7 opened this issue Oct 28, 2020 · 10 comments

Comments

@maxmil7
Copy link

maxmil7 commented Oct 28, 2020

I have submitted a PR to the fork @pid was maintaining to mark it as deprecated.
pid#5

Can you please publish a new version (possibly v3.2.0) of the module
I believe we would just have to merge the above PR and update the repo description once a new version has been published.
Thanks!

@karanlyons
Copy link
Owner

I’d need to get the murmurhash3js name from npm in order to do so. There is a process for this, but I haven’t had time to go through it.

@maxmil7
Copy link
Author

maxmil7 commented Oct 29, 2020

ah i see. Is it not possible for @pid to add you as an owner so you can publish the package?

@karanlyons
Copy link
Owner

It is indeed, though they may not be available to use this process.

@qix
Copy link

qix commented Nov 3, 2020

This package seems valuable though, perhaps instead you could publish it under a different name?

The proper support for UTF-8 is a super important issue with the old library. It makes it very difficult to port existing databases that were using Murmurhash on JavaScripts UTF-16.

@karanlyons
Copy link
Owner

What I could do is begin the dispute resolution process. @pid and I had discussed doing a changeover in the past but one or both of us got swamped with other things and so we never made the hand off.

@xboxfly15
Copy link

Has any progress been made in regards to publishing to NPM? I'm currently in need of this package

@polarathene
Copy link

You can add a github repo into your package.json instead of an NPM package to use it in the meantime. Or an alternative NPM package name could be used if it doesn't look like it'll have success reclaiming the original package name.

When I was looking into which package to use, it was a bit confusing with all the choices present, then discovering the maintenance and fork history involved to end up realizing this is the project that you probably would want to use. Probably not much that can be done about that discovery issue without getting ownership of the NPM package name unfortunately.

@Ayc0
Copy link

Ayc0 commented Jun 2, 2021

What about uploading the built files to GitHub packages? so that people can already start to use the new version of this library even if the name isn't available on NPM yet?

@matheus23
Copy link

Hey, what's the status of this? I'm looking into having a murmur3 package that gives me 128bit hashes as Uint8Arrays which match the reference implementation. This is exactly what I'm looking for. I'd love to have it on npmjs. ♥️

@matheus23
Copy link

It seems like technically the package is under your control, you only need to publish: https://www.npmjs.com/~karanlyons

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

7 participants