Md. Moniruzzaman

> 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...

> 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...

> 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...

No the isssue is not fixed i used the earlier versions. without asar, `asar:false`

I have build for node 14 and electron 13 works on development but not after build. [iohook-v0.9.3-electron-v89-win32-x64.tar.gz](https://github.com/wilix-team/iohook/files/7112391/iohook-v0.9.3-electron-v89-win32-x64.tar.gz) [iohook-v0.9.3-node-v83-win32-x64.tar.gz](https://github.com/wilix-team/iohook/files/7112392/iohook-v0.9.3-node-v83-win32-x64.tar.gz) asar: true  asar: false