Skip to content
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

bigint: Failed to load bindings #154

Open
JaneX8 opened this issue Feb 14, 2023 · 3 comments
Open

bigint: Failed to load bindings #154

JaneX8 opened this issue Feb 14, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@JaneX8
Copy link

JaneX8 commented Feb 14, 2023

Bug Report: bigint: Failed to load bindings

Describe the bug

When running the application, the following error message is displayed:

stderr: bigint: Failed to load bindings, pure JS will be used (try npm run rebuild?).

How to reproduce

Steps to reproduce the behavior:

Install this package and run the provided example from README.

Expected behavior

The application should start without any errors or warnings. I would like to disable or suppress this.

Additional context

Operating System: Windows 11 and Linux
Node.js version: 18.x

@JaneX8 JaneX8 added the bug Something isn't working label Feb 14, 2023
@gnarea
Copy link
Member

gnarea commented Feb 15, 2023

Thanks for taking the time to report this @JaneX8!

This is the first time I see that message. I've never seen it on CI (I just checked) and it doesn't happen on my computer either.

Here's a screenshot from CI:

win

And this is what I get on my computer:

$ rm -rf node_modules/

$ node -v
v18.5.0

$ npm i

added 1193 packages, and audited 1194 packages in 12s

264 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

This appears to be the cause: no2chem/bigint-buffer#31. If so, the solution appears to be to pre-install certain build tools depending on your OS.

@JaneX8
Copy link
Author

JaneX8 commented Feb 15, 2023

No problem. It seems to work properly even with the error showing. I could install the build tools locally however I deploy my functions (obviously without all the dev and build tools) to a serverless platform. Meaning the logging there will continue to contain this error all the time.

Therefore I'd like to find a way to simply disable the thing that causes this or suppress this error.

@gnarea
Copy link
Member

gnarea commented Feb 15, 2023

Unfortunately, other than replacing bigint-buffer, I can't think of anything we can do from this library.

I implemented dnssec-js fairly recently and that was the best bigint/buffer library I could find, but I could've missed a better one or one may have been released since, so if that's the case please let me know and I may consider replacing bigint-buffer with it.

Otherwise, if you want to get rid of the warning I think the best course of action may be to propose a PR to fix no2chem/bigint-buffer#31.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants