Ahmed Elshafey

> Allowing node integration is not a recommended security practice, neither is disabling context isolation. > > https://www.electronjs.org/docs/tutorial/security#2-do-not-enable-nodejs-integration-for-remote-content > https://www.electronjs.org/docs/tutorial/security#3-enable-context-isolation-for-remote-content > > I understand it's the only way around this...

@abacaj can you provide an example of how you did it?

> Yes I have a working example here: https://github.com/abacaj/iohook-sample > > You can see what I changed here: [abacaj/iohook-sample@0094c4c](https://github.com/abacaj/iohook-sample/commit/0094c4c3e733337f5733d80f1cb6360b86c2535f) > > If you `yarn install` and then `yarn start`, you...

Right now, not that I'm aware of. You can register a `mousemove` listener inside a `keydown` listener but that would probably only trigger on mouse move after `keydown` which is...

You're using Node 16 which has ABI 93, currently iohook isn't prebuilt for that version which is why you get the issue. This is in the pipeline.

Is this still an issue?

> yes, the same issue > > "iohook": "^0.9.3", > >  What's your environment please? Node/electron version, os, etc.

> Thanks for response, > Don't worry, I solved my issue by using other library Could you share it with us so others running into your use case can use...

This is unfortunately the state for 13, there are more issues using iohook in electron 13 that even when it does build it breaks in runtime. I'm working on the...

This is not at all related to iohook and shouldn't be. There are other solutions to get an HID device vendor and product ID and you can do your logic...