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

Failed to load bindings, pure JS will be used #31

Open
mytecor opened this issue Mar 4, 2021 · 4 comments
Open

Failed to load bindings, pure JS will be used #31

mytecor opened this issue Mar 4, 2021 · 4 comments

Comments

@mytecor
Copy link

mytecor commented Mar 4, 2021

1.1.5 on windows

@gnarea
Copy link

gnarea commented Feb 15, 2023

According to trufflesuite/ganache#1080 (comment), this warning can be avoided by having the build tools pre-installed.

@jmrossy
Copy link

jmrossy commented Oct 8, 2023

Same on MacOS

@jmrossy
Copy link

jmrossy commented Oct 8, 2023

GIven that fallback to pure JS is possible, it seems like this line just creates noise and confusion: https://github.com/no2chem/bigint-buffer/blob/master/src/index.ts#L16

I'd recommend simply removing it. It's better if libs like this don't log to console. If you really want to log anyway, you can use a lib like debug and log under your namespace, so devs can optionally enable that logging as desired.

@silasdavis
Copy link

It is problematic when a library starts emitting unsolicited warnings to stderr. For example I am running a script as a form of FFI from a virtual machine. That virtual machine interprets non-empty stderr as a reason to halt. We also may explicitly wish to use the pure JS version, our downstream users shouldn't be issued this as a warning.

Looks like it would be straight-forward to provide a mechanism to opt out of this warning WarnOnPureJS = true could be the default, then anyone wishing to disable that can set it globally to false.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants