Could not detect abi for version 12.0.1 and runtime electron. Updating "node-abi" might help #14
Description
An unhandled error has occurred inside Forge: Could not detect abi for version 12.0.1 and runtime electron. Updating "node-abi" might help solve this issue if it is a new release of electron
Error: Could not detect abi for version 12.0.1 and runtime electron. Updating "node-abi" might help solve this issue if it is a new release of electron
at Object.getAbi (/home/user/repos/archivebox-desktop/node_modules/node-abi/index.js:30:9)
at new Rebuilder (/home/user/repos/archivebox-desktop/node_modules/electron-rebuild/src/rebuild.ts:112:44)
at rebuildWithOptions (/home/user/repos/archivebox-desktop/node_modules/electron-rebuild/src/rebuild.ts:363:21)
at doRebuild (/home/user/repos/archivebox-desktop/node_modules/electron-rebuild/src/rebuild.ts:416:12)
at asyncFn (/home/user/repos/archivebox-desktop/node_modules/@electron-forge/core/src/util/rebuild.ts:15:23)
at /home/user/repos/archivebox-desktop/node_modules/@electron-forge/async-ora/src/ora-handler.ts:35:5
at new Promise (<anonymous>)
at asyncOra (/home/user/repos/archivebox-desktop/node_modules/@electron-forge/async-ora/src/ora-handler.ts:34:10)
at _default (/home/user/repos/archivebox-desktop/node_modules/@electron-forge/core/src/util/rebuild.ts:14:9)
at _default (/home/user/repos/archivebox-desktop/node_modules/@electron-forge/core/src/api/start.ts:44:9)
at /home/user/repos/archivebox-desktop/node_modules/@electron-forge/cli/src/electron-forge-start.ts:58:19
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! archivebox-desktop@1.0.0 start: `electron-forge start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the archivebox-desktop@1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/user/.npm/_logs/2021-03-16T22_13_51_504Z-debug.log
Not sure if it was just a problem on my end. Happened on a fresh install after running npm start step following steps in readme.
Ended up fixing with a npm update --depth 100
I think it's a problem with a dependency of a dependency, not necessarily anything wrong in this project