Skip to content
New issue

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

Could not detect abi for version 14.0.0 and runtime electron #845

Closed
malept opened this issue Aug 31, 2021 · 1 comment · Fixed by #847
Closed

Could not detect abi for version 14.0.0 and runtime electron #845

malept opened this issue Aug 31, 2021 · 1 comment · Fixed by #847
Labels

Comments

@malept
Copy link
Member

malept commented Aug 31, 2021

There is a problem with automatically releasing new versions of node-abi, which is why this error exists with electron-rebuild (and Electron Forge, by extension), even though electron-rebuild depends on the latest version of node-abi (2.30.0, at the time of the creation of this issue). This cannot be fixed until a new release is made (2.30.1 or later).

Workaround

Electron Forge

Electron Forge uses electron-rebuild to rebuild native modules. In your Electron Forge config, set forceABI: 89 in electronRebuildConfig. For example, if your config is in package.json (note that this is a partial config shown, only meant to indicate where the option goes):

{
  "config": {
    "forge": {
      "electronRebuildConfig": {
        "forceABI": 89
      }
    }
  }
}

electron-rebuild API

Set forceABI: 89 in the RebuildOptions.

electron-rebuild CLI

Add --force-abi=89 to your command line flags.

@electron electron locked and limited conversation to collaborators Aug 31, 2021
@malept malept pinned this issue Aug 31, 2021
@electron-bot
Copy link

🎉 This issue has been resolved in version 3.2.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

@malept malept unpinned this issue Sep 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants