We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, I tried bulldohzer on an up-to-date arch linux, but I get the following error:
LC_ALL=C nvm exec 12 -- npx bulldohzer --doh Running node v12.20.1 (npm v6.14.10) In file included from ../notify.cc:4: /home/m/.cache/node-gyp/12.20.1/include/node/node.h:737:7: warning: cast between incompatible function types from 'void (*)(v8::Local<v8::Object>)' to 'node::addon_register_func' {aka 'void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)'} [-Wcast-function-type] 737 | (node::addon_register_func) (regfunc), \ | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /home/m/.cache/node-gyp/12.20.1/include/node/node.h:771:3: note: in expansion of macro 'NODE_MODULE_X' 771 | NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage) | ^~~~~~~~~~~~~ ../notify.cc:72:1: note: in expansion of macro 'NODE_MODULE' 72 | NODE_MODULE(addon, Init) | ^~~~~~~~~~~ [prebuilt-bindings] => Prebuilt bindings installed! Trace: TypeError: doh.replace is not a function at /media/data/m/dotfiles/node/.npm/_npx/12826/lib/node_modules/bulldohzer/source/cli.js:356:13
Note: I ran it with nvm to ensure this is not related to a specific node version, but the same error occurs when ran outside nvm
The text was updated successfully, but these errors were encountered:
I got this same error, I believe it's because --doh and --dns require a list of resolvers to use such as npx bulldohzer --doh cloudflare
--doh
--dns
npx bulldohzer --doh cloudflare
Sorry, something went wrong.
No branches or pull requests
Hi, I tried bulldohzer on an up-to-date arch linux, but I get the following error:
Note: I ran it with nvm to ensure this is not related to a specific node version, but the same error occurs when ran outside nvm
The text was updated successfully, but these errors were encountered: