You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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.
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.
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
The text was updated successfully, but these errors were encountered: