Marcel Blum

You can use `require.resolve('iohook')` to find out where the runtime is looking for the missing iohook.node file. Note that @ash0x0 has stated that it won't work in Electron 13 without...

Sorry you can try `require.resolve.paths("iohook")`. I don't know what 78200 could mean in this context but I see it also appears in your error screenshots above ("...at Object.78200"). I don't...

FWIW I have an Electron 12 project that uses iohook and `asar:true` successfully. I use Electron Forge for building and I make sure *.node and *.dll files are excluded from...

If you added the `"iohook": {"targets": [...` to your package.json *after* installing iohook, you probably just need to reinstall iohook, that way its install script will detect the needed versions...

Sorry I don't have experience using the Webpack plugin in Forge but that may be the source of your issue, the Webpack docs on externals says: > The externals configuration...

@deepanshushukla I'm not really sure what you're asking me to test at that template link. I'm not that familiar with Webpack (and honestly don't understand why it would be used...

Looks like you're using Electron 16.0.0 not 6.0.0, correct? iohook doesn't yet offer prebuilds for Electron 16 but you can build it manually. However it can only work in the...

https://wilix-team.github.io/iohook/manual-build.html

You'll get best results cloning the iohook repo and building from there rather than building from `/node_modules/` inside another project. Try cloning the repo, then `npm install`, then `node build.js...

I don't understand your question. Looks from your screenshot like you successfully built the binaries. Next copy them into your project's `/node_modules/iohook/` folder so you can use them there. For...