murmurHash3.js icon indicating copy to clipboard operation
murmurHash3.js copied to clipboard

Please publish a new version of this module

Open maxmil7 opened this issue 4 years ago • 10 comments

I have submitted a PR to the fork @pid was maintaining to mark it as deprecated. https://github.com/pid/murmurHash3js/pull/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!

maxmil7 avatar Oct 28 '20 23:10 maxmil7

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.

karanlyons avatar Oct 29 '20 03:10 karanlyons

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

maxmil7 avatar Oct 29 '20 05:10 maxmil7

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

karanlyons avatar Oct 30 '20 02:10 karanlyons

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.

qix avatar Nov 03 '20 03:11 qix

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.

karanlyons avatar Nov 03 '20 05:11 karanlyons

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

xboxfly15 avatar May 11 '21 00:05 xboxfly15

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.

polarathene avatar May 11 '21 07:05 polarathene

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?

Ayc0 avatar Jun 02 '21 15:06 Ayc0

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. :hearts:

matheus23 avatar Aug 20 '21 12:08 matheus23

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

matheus23 avatar Aug 20 '21 12:08 matheus23