-
-
Notifications
You must be signed in to change notification settings - Fork 69
Failed to load native bindings on linux x64 platform #431
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
Comments
Can you provide a reproduction? And provide |
The repro will take me a while probably |
In the meantime, you can use |
Sounds good thanks. I'll work on the repro tonight or tomorrow my time Appreciate your help and responsiveness! |
@JounQin I figured it out while making the reproduction. With vanilla npm all is fine. My company has an internal artifactory for npm which hosts specific versions of packages. there is a delay of packages to scan for vulnerabilities, etc. 1.5.0 of
So for anyone who finds this in the future, make sure to check that all packages are actually available in your npm registry. If they are not, they will not auto-install and this will fail semi-silently. Closing this as resolved, this case everything was on my side. Might be nice to add a debug flag to Thanks again 🙏🏼 |
Indeed! |
Creating this issue from #405
Originally posted by @ckifer in #405
Info:
process.platform is
linux
,x64
,isMusl
is falsenativeBinding
is always undefined, loaderErrors are:I set
NAPI_RS_FORCE_WASI
to true and then:Error: Cannot find module '@unrs/resolver-binding-wasm32-wasi'
Error: Cannot find module './resolver.wasi.cjs'
Installing
@unrs/resolver-binding-linux-x64-gnu
fixes the issue but then makes builds on MacOS fail.Attempted to upgrade npm to 10.x and this still failed. Cannot upgrade npm further or use different package managers due to company restrictions
The text was updated successfully, but these errors were encountered: