Temp fix for issue #2042 based on #667's solution

[alex-drocks]

Preflight Checklist

• I have read the contribution documentation for this project.
• I agree to follow the code of conduct that this project follows, as appropriate.
• I have searched the issue tracker for a bug that matches the one I want to file, without success.

Issue Details

• Electron Forge Version:
  • 6.0.0-beta-54
• Electron Version:
  • 11.2.1
• Operating System:
  • Windows 10 pro, Version 20H2, released date 2020-09-15, 19042.746
• Last Known Working Electron Forge version::
  • 6.0.0-beta-54 (with Electron v10)

Expected Behavior

npm run start should start the electron app as usual.

Actual Behavior

npm run start fails with Could not detect abi for version 11.0.1 and runtime electron.

To Reproduce

Not applicable: based on prior proof contained in issue #2042

Additional Information

• I have followed issue node-abi needs to be updated #667's solution and it works.

• To temporarily fix the issue on your machine without waiting for an official release of Forge, you can try deleting your project's node_modules completely and also the package-lock.json if you use npm (for yarn delete yarn lock or something similar).

• Then, in your projects folder run npm install and it should not throw the node-abi error anymore.

[malept]

This isn't really something that can be fixed in Electron Forge itself. As mentioned in other bugs, you need to update the node-abi dependency. Although as of electron-rebuild >= 2.3.4, node-abi is only called if there's actually a native module to rebuild.