node-abi needs to be updated
See original GitHub issueCurrently, running electron-forge start
with electron
version 4.x.x
gives the error
An unhandled error has occurred inside Forge:
Could not detect abi for version 4.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 4.0.1 and runtime electron. Updating "node-abi" might help solve this issue if it is a new release of electron
at Object.getAbi (C:\node_modules\node-abi\index.js:30:9)
Is there much that needs to be changed before electron-forge
supports electron 4.x.x
?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
node-abi needs to be updated · Issue #667 · electron/forge
Currently, running electron-forge start with electron version 4.x.x gives the error An unhandled error has occurred inside Forge: Could not ...
Read more >node-abi - npm
Get the Node ABI for a given target and runtime, and vice versa.. Latest version: 3.30.0, last published: 25 days ago. Start using...
Read more >"node-abi" problem with MM v2.18.0 - MagicMirror Forum
Hello everyone, after updating to MagicMirror v2.18.0, a couple of modules show some errors related with “node-abi”.
Read more >@frida/node-abi - npm Package Health Analysis | Snyk
We found that @frida/node-abi demonstrates a positive version release cadence with at least one new version released in the past 3 months.
Read more >Upgrading Electron from 7 to 12 - DEV Community
In case node-abi is not the latest, upgrade it: npm update node-abi --depth 2 ... So, you have to specify options like so:....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For anyone else that runs into this problem and if you’re using yarn: go into yarn.lock file, find entry for
node-abi
, delete it, then re-runyarn
.See https://github.com/yarnpkg/yarn/issues/4986#issuecomment-395036563
I did a fresh installation with current version and I’m getting an updated version of this error:
modifying the yarn.lock file is not helping