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
node-gyp not rebuilding correctly #404
Comments
It would be great if you could provide a minimal testcase for this that we could add to the testsuite, to avoid any regressions in the future. |
I have the same issue when rebuilding native module 'serialport'. |
Can confirm @malept 2.0.2 is not working correctly. Had to downgrade to 2.0.1 |
Proposed fix in #409, please test. For those using yarn, use dependency resolutions to point to the branch name. |
As a small datapoint, PR #409 works for |
I can confirm that #409 fixes our build. 🎉 |
🎉 This issue has been resolved in version 2.0.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
For some reason I can't confirm the fix. Here is a reproducible build with the latest version to compile nodegit: https://github.com/Githubber2021/node_module_version-issue
|
Not sure what you're trying to show in your repro instructions, that makes sense since you're trying to use a native module compiled for Electron 10 with AVA running with whatever Node.js version, which will never have the same ABI version number. |
Thanks! Just a few minutes ago I noticed that Electron has a different ABI version than node.js and I don't understand why. For instance node version I can delete my posts here on request since its very off-topic. Sorry for the noise |
My understanding is that Electron uses BoringSSL instead of OpenSSL, which changes the ABI surface. |
Native dependency detection appears to be breaking in v2.0.2.
electron-rebuild no longer correctly identifies all the native dependencies needed to be rebuilt.
Reverting back to v2.0.1 fixes the issue.
I will do some more digging into the problem, but the issue is probably related to the changes in 9d166a8
The text was updated successfully, but these errors were encountered: