search

neilgupta / Sherlock

Natural-language event parser for Javascript
https://sherlock.neil.gg
MIT License
532 stars 32 forks source link

SherlockJS NPM different source #16

Closed danjford closed 7 years ago

danjford commented 7 years ago

I was looking through NPM and noticed that Sherlock is there but it seems to be coming from another source: https://github.com/maytis/sherlockjs.

Is that project related to this one or is it separate as it probably isn't getting the benefits of any updates made to this project?

neilgupta commented 7 years ago

Unfortunately, that's somebody who forked my code and just removed all references/copyright notices. I'd love to push to npm but they've taken the sherlockjs name. I've asked them (https://github.com/maytis/sherlockjs/issues/2) to remove the project so I can push the updated version to npm.

danjford commented 7 years ago

That's a shame, if it can't be resolved you could try NPM support? As it is the same library and the other one hasn't been updated in 2 years perhaps they'll be able to give you permission to publish new versions to the old namespace?

h-dong commented 7 years ago

Considering it hasn't been resolved yet, any chance it is possible to publish this on NPM with a different name? e.g. sherlock-js or something ?

danjford commented 7 years ago

Did you try contacting support @neilgupta? I think if NPM respond with unhelpful response then perhaps as @hdong92 suggested, publishing to sherlock-js might be the best answer.

danjford commented 7 years ago

Or another approach could be to create a free NPM organisation called sherlock and publish sherlock under core so that people can install it via npm install @sherlock/core and then watson could be published and used through @sherlock/watson or something similar.

neilgupta commented 7 years ago

Sorry for the delay, I've been incredibly busy lately. I just began the dispute resolution process with NPM, but publishing under an organization or just as sherlock-js sound like good fallbacks if that fails.

The other issue is that Sherlock will need to be refactored to support Watson as an NPM module. I won't have time to work on that any time soon, but if somebody can help with that, that would be great. Otherwise, I can publish Sherlock without Watson support to NPM for now.

neilgupta commented 7 years ago

I gained access to https://www.npmjs.com/package/sherlockjs and have updated it with the latest Sherlock version. You can now just use npm install sherlocks. I will keep it updated it with future releases. Thanks for your patience, everyone!