-
Notifications
You must be signed in to change notification settings - Fork 178
fix: use 'target_arch' for node-pre-gyp #1115
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
fix: use 'target_arch' for node-pre-gyp #1115
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #1115 +/- ##
==========================================
+ Coverage 76.78% 77.06% +0.27%
==========================================
Files 21 21
Lines 741 763 +22
Branches 140 142 +2
==========================================
+ Hits 569 588 +19
- Misses 121 122 +1
- Partials 51 53 +2 ☔ View full report in Codecov by Sentry. |
aea4654 will unfortunately cause the binaries to be redownloaded each time a rebuild occurs. node-pre-gyp doesn't update the binary without the |
@samuelmaddock is there a way that we can be smarter here for them? E.g. detect a .node file with the wrong arch and nuke it Not super fussed but would be nice if it's not too hard |
7129520
to
cbd44e4
Compare
🎉 This PR is included in version 3.4.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
The arguments provided to node-pre-gyp are incomplete, resulting in prebuilt binaries not downloading the correct architecture. From the readme,
--target_arch
and--target_platform
are both used for downloading the prebuilt binaries. The--arch
option seems to only be used when falling back to thenode-gyp
local build.Also, if the binary already exists,
--update-binary
is required to redownload in the case of changing the targeted architecture.Follow up to #1095