What is the relation between `keyv` and `@keyvhq/keyv` projects?
michaelrambeau opened this issue · 5 comments
Hello,
I run Best of JS site where Keyv project is tracked as a repo from Luke Childs.
So it seems there are 2 Keyv projects:
- Original: https://github.com/lukechilds/keyv
keyvon NPM - Yours: https://github.com/microlinkhq/keyv
@keyvhq/keyvon NPM
Same name, almost same logo (blue VS red), same description in the README.md... it's a bit confusing!
Which one is the right Keyv? Or what is the relation between both projects?
Sorry if I missed something obvious, I suppose it's a fork because the orginal one might be not maintained but I couldn't find any clarification, the following issue does not explain anything about the reason why moving from keyv to @keyvhq/keyv.
Thank you for the clarification.
I hope I will not have to track 2 different Keyv projects in Best of JS 😅 !
Screenshot (Original)
Screenshot (Yours)
Hello, keyv by lukechilds is the original project ( last updated in sept 2020 ), the original author become busy with other work, so we forked it to make this repo, I will update the readme and add proper attribution as well
I suppose it's a fork because the original one might be not maintained
Exactly that 🙂
It looks like the original got picked back up at https://github.com/jaredwray/keyv. Is there still some delta in functionality that makes it worthwhile to maintain this fork? If so, is it something that could be merged into that "upstream" repo so this one could be deprecated? I think it's still confusing to have both of these projects existing. E.g. when I google "keyv", my first result is the original package on npmjs.com, and my second is documentation for this project on js.org.
Just found this confusing too....which should I use?
Both projects are quite different and point. Evaluate them and use whatever you want 🙂