Consider hotkey libraries other than react-hotkeys

[tntmarket]

roam-toolkit currently uses https://github.com/greena13/react-hotkeys to listen to keys.

It works well for the most part, but various bugs made vim style bindings harder to implement:

• [BUG] Single key getting activated on multi-key sequence greena13/react-hotkeys#234
• Support case-insensitive hotkeys greena13/react-hotkeys#249
• [BUG] Sequences in keyMap prevent combinations from working greena13/react-hotkeys#229
• [BUG] Sequences like 'g' then '1' kills every other hotkeys after first execution greena13/react-hotkeys#255

Also, react-hotkeys is no longer actively maintained.

This deliverable here would be evaluating other options, and seeing how much there is to be gained by switching.

Other options:

https://github.com/ccampbell/mousetrap

• Seems moderately/low activity? Decent number of old open issues

https://github.com/jaywcjlove/hotkeys

• The API doesn't have key sequences built it
• I personally find the DX of react-hotkeys a little more convenient.

Help maintain react-hotkeys

Roll our own hotkey library

[houshuang]

I've used mousetrap in the past, with no issues. Not very complex usage though (no keychords etc) but actively used as core feature of my app for several years.

[ZYinMD]

react-hotkeys v1.x uses mousetrap, and had reached a very stable state before v2 was published.

[mgsloan]

Another vote for mousetrap here. Though, it does have some smelly bits. For example, when developing my todoist-shortcuts browser extension, I noticed that it has an arbitrary time limit of 1 second for completing a key sequence, so my fork removes that.

[Stvad]

@mgsloan the details of the underlying library are mostly abstracted away. So I don't think the dev experience would differ that much between the options.
https://github.com/roam-unofficial/roam-toolkit/blob/master/CONTRIBUTING.md introduces some overview of current code structure and conventions. Would be happy to answer more detailed questions on that as-well (reply mostly to previous version of the comment ;) )

[mgsloan]

Cool, thanks for the info @Stvad. I'd edited my comment because I realized this isn't the spot to discuss my rather idiosyncratic case, which is instead tracked by #91