Marcel Blum

When you do `npm install iohook` only the essential "prod" part of the library is installed inside `node_modules/iohook`. When you clone the iohook repo you get the complete library source...

Check the docs for supported targets, Electron 13 is not yet supported https://wilix-team.github.io/iohook/installation.html

You can do a [manual build](https://wilix-team.github.io/iohook/manual-build.html) of iohook on an Apple Silicon Mac and it works perfectly (as far as I can tell so far, been testing it on an...

Yeah that was a longstanding Windows iohook bug that was only recently fixed in v.0.9.x. If you try to run any 2 apps simultaneously that use any older version of...

It does work if you build it manually. Just did it earlier today :) Clone the full repo, `npm install`, then `node build.js` for your desired target as detailed at...

If you were able to get to the point of making a working build then you're already 90% of the way there :) What is the exception thrown when you...

@ondoki that's one way to do it. The reason `npm install` fails is because you are running an arch/version of Node not yet officially supported by iohook. The install script...

Can you provide the build command line you were trying? And provide some more context to those error messages? You mentioned Electron but your errors reference the iohook build for...

When iohoook installs, it tries to detect your current environment and download prebuilt binaries for your platform. As of now prebuilds are only available for up to Node v15 (abi...

@sancarn those log messages are from this function https://github.com/wilix-team/iohook/blob/e584b64aa0dcc0e2f9acc5f5dab37fe7241c4c68/libuiohook/src/windows/input_helper.c#L469 And they are not errors in and of themselves rather they are expected log output. While they're not an indication of...