We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm trying to build for node version 18.13.0 and Electron 22.0.0 but i get the following error:
node build.js --upload=false 70% 1 Mbps ─╯ Building iohook for node v18.13.0>>>> node:events:491 throw er; // Unhandled 'error' event ^ Error: spawn /home/scorpion197/chronly-test/chronly-electron/node_modules/iohook/node_modules/.bin/node-gyp ENOENT at ChildProcess._handle.onexit (node:internal/child_process:283:19) at onErrorNT (node:internal/child_process:476:16) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) Emitted 'error' event on ChildProcess instance at: at ChildProcess._handle.onexit (node:internal/child_process:289:12) at onErrorNT (node:internal/child_process:476:16) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { errno: -2, code: 'ENOENT', syscall: 'spawn /home/scorpion197/chronly-test/chronly-electron/node_modules/iohook/node_modules/.bin/node-gyp', path: '/home/scorpion197/chronly-test/chronly-electron/node_modules/iohook/node_modules/.bin/node-gyp', spawnargs: [ 'configure', 'rebuild', '--target=18.13.0', '--arch=x64', '--v8_enable_pointer_compression=1', '--build_v8_with_gn=false', '--enable_lto=false' ] } Node.js v18.13.0
The text was updated successfully, but these errors were encountered:
Have you solved this?
Sorry, something went wrong.
@Scorpion197 , @LiuZhenyan-Wuzhong , did you find any solution
@Ankit-Devslane nope I ended up with writing something similar in Rust
No branches or pull requests
I'm trying to build for node version 18.13.0 and Electron 22.0.0 but i get the following error:
The text was updated successfully, but these errors were encountered: