webtorrent/webtorrent-desktop

Crashes when starting

K0-RR opened this issue · 1 comments

What version of WebTorrent Desktop are you using?
0.24.0
What operating system and version?
Alpine Linux 3.19
What happened?
I wanted to run from git because I don't use distro with deb or rpm packages.

core% npm start    

> webtorrent-desktop@0.24.0 start
> npm run build && electron --no-sandbox .


> webtorrent-desktop@0.24.0 build
> babel src --out-dir build

Successfully compiled 65 files with Babel (617ms).
node:events:497
      throw er; // Unhandled 'error' event
      ^

Error: spawn /home/k0rr/webtorrent-desktop/node_modules/electron/dist/electron ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:286:19)
    at onErrorNT (node:internal/child_process:484: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:292:12)
    at onErrorNT (node:internal/child_process:484:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn /home/k0rr/webtorrent-desktop/node_modules/electron/dist/electron',
  path: '/home/k0rr/webtorrent-desktop/node_modules/electron/dist/electron',
  spawnargs: [ '--no-sandbox', '.' ]
}

Node.js v21.4.0
core% npm audit fix
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: webtorrent-desktop@0.24.0
npm ERR! Found: react@17.0.2
npm ERR! node_modules/react
npm ERR!   react@"17.0.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^15.4.0 || ^16.0.0" from material-ui@0.20.2
npm ERR! node_modules/material-ui
npm ERR!   material-ui@"0.20.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:

What did you expect to happen?
App starting
Are you willing to submit a pull request to fix this bug?
no

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?