-
Notifications
You must be signed in to change notification settings - Fork 15.9k
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
[Bug]: electron-builder install-app-deps failing post electron upgrade to v32.0.0 and v32.0.1 #43510
Comments
I feel like I bumped into this bug as well. It seems to be something with the integration of node-gyp and the V8 engine. I tried to install pokusew/nfc-pcsc which down the line relies on pcsclite. All issues disappear when downgrading to electron 31...
|
Hello Team, |
The Electron core team is not responsible for electron-builder - please open the issue on that repo. |
But this is not
The on all OSs, I get this:
Downgrading to 31.x fixes the above issues |
Hi Team, The issue is not related to electron-builder but has a lot to do with the upgraded electron version 32.x.y. Please support us in resolving the issue. PS: Please don't close the issue, without addressing our problems. Regards, |
Related issue posted here: WiseLibs/better-sqlite3#1225 |
So it this a electron builder problem or what ? i cant built duo this error. Im now unsure if electron version is at fault or if electron builder needs an update ? anyway guess I will have to fallback to 31 for now C++20 or later required." |
Same issue: also MacOS, encountered this with electron-forge on v32. Downgrading to |
Chiming in here from the electron-builder side. Can you test on latest/next v25.x? (if not having done so already) |
I'm on latest 32.x electron and latest 25.x electron-builder, same issue. |
Same issue. The native module rebuild works with Electron 31, but C++20 error with Electron 32 |
Solution: migrate from NAN to NAPI, or if you must use NAN then simply patch |
@danielweck thanks for your answer but as I see the given library has already been using NAPI, right? |
The OP's stacktrace shows NAN references, which fail to compile. NAPI works out of the box, in my Electron v32 project :) Frankly the effort of migrating from NAN to NAPI is well worth it, if anything for the ABI portability advantages (i.e. no need for strict version match that otherwise require a complete rebuild against the exact runtime revision), but also because it is the recommended modern method to build NodeJS / Electron native add-ons, using a well-maintained abstraction library (unlike NAN which seems to accumulate technical debt more often). |
I have the same issue |
Preflight Checklist
Electron Version
v32.0.1
What operating system(s) are you using?
macOS
Operating System Version
macOS Sonoma 14.6.1
What arch are you using?
arm64 (including Apple Silicon)
Last Known Working Electron version
31.1.0
Expected Behavior
When upraded electron to v32.0.0 or v32.0.1, the npm install command fails with the following error
Actual Behavior
npm install shouldn't fail after upgrading electron.
Testcase Gist URL
No response
Additional Information
Here is my package.json file with all the dependencies
The text was updated successfully, but these errors were encountered: