New Maintainers Needed

[greena13]

Hi all,

I have not had as much time as I'd like to work on this library in recent months and it is looking to be a similar situation for at least the next few months. Meanwhile, the issues continue to pile up.

I'm looking for some assistance in helping to investigate and solve outstanding issues with the project. I'm hoping to be available to support and guide fellow contributors, to point them in the right direction and explain high-level concepts.

[mayank23]

Hi @greena13 my team is using react-hotkeys and if possible I would like to help maintain

[greena13]

Hi @mayank23, apologies for the (significant) delay in getting back to you. I'll be looking to move on maintenance of this package this year to any interested party, so I am no longer the bottleneck for addressing the many outstanding issues.

Are you still interested and have the resources to help out?

Thanks. I will be proactive in keeping an eye on this thread, so it won't be months before getting back to you, again.

[ZYinMD]

@greena13 I suggest changing the beginning of README a little bit.

I think a "looking for maintainers" section in the beginning of README has a negative effect of pushing new users away, because they'd think "this package is abandoned, let's not try it", it'd be better to change the beginning of README into:

===================

v1.x vs v2:

If you only need some basic usage of hotkeys, you can use v1.1.4. It is very stable. For documentation of v1.x, see here.

Upgrading from 1.x ?

If you need the advanced features provided in v2, see the upgrade notes.

V2 is looking for maintainers:

We are is search of new maintainers to help address issues in v2. If you are interested in helping out in any capacity, please get in touch.

===================

This way new users who just found this package will be much less likely to go away.

[InputNeuron]

We're going to need a new maintainer apparently ;)

[InputNeuron]

... or an intermediate strategy and maybe someone can fork and start merging PRs?

[InputNeuron]

No disrespect to @greena13 implied - I'm sure he's busy... but we should consider an official fork for this. Lots of bugs an PRs are outstanding here

[joepsyko]

any news on this?

[fynncfchen]

Hey I'm a heavy user of this library, still need a new maintainer here?

[aeksco]

I'm also interested in lending a hand - I use this package in several personal + professional projects and would like to help on the maintenance front if I can. I've secured the react-hotkeys GitHub organization - it might make sense to relocate the repository into a space where multiple maintainers could work in parallel to ensure that this repo stays alive and well.

Perhaps it would make sense to organize a call for interested parties?

[tstirrat15]

I like that idea. I haven't seen another library that I like as much as this one, and I'd hate to see it die. Any way I can help push it along?

[romellem]

If react-hotkeys is effectively abandoned, are there any good forks or alternatives that people recommend?

Love the library by the way, hopefully this can be brought back, but no worries if it doesn't. Thanks for all the work!

[JCDuann]

Hi @greena13, I'm Jiacheng Duan (@JCDuann on GitHub). I saw this issue and the README note that react-hotkeys is looking for new maintainers. I'd like to help with real maintenance work.

I understand this library is still used by many projects, so I would start conservatively and focus on maintenance rather than changing direction:

• triage open issues and identify duplicates/stale reports
• review open PRs and separate low-risk fixes from breaking changes
• reproduce high-impact bugs and write clear reproduction notes
• improve tests and documentation around supported React/browser behavior
• prepare small, reviewable PRs before asking for broader permissions

I'm also applying for OpenAI's Codex for Open Source program, and if I'm accepted I'd use the credits only for this project's maintenance workflow: issue triage, PR review assistance, test generation, release notes, and regression-risk analysis.

If you're open to it, I'd like to start by helping triage issues/PRs and earn trust through visible work before receiving any maintainer permissions.
Update: I also opened a concrete first maintenance PR to make the project install, test, and build reliably with modern npm/Node and on Windows: #352. The local verification for that PR was npm test (2102 passing) and npm run build-cjs.