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
Error of
npm error /redacted/Library/Caches/node-gyp/22.9.0/include/node/v8-local-handle.h:269:19: error: static assertion failed due to requirement 'std::is_base_of<v8::Value, v8::Data>::value': type check npm error 269 | static_assert(std::is_base_of<T, S>::value, "type check"); npm error | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm error ../node_modules/nan/nan_callbacks_12_inl.h:175:20: note: in instantiation of function template specialization 'v8::Local<v8::Value>::Local<v8::Data>' requested here npm error 175 | cbinfo(info, obj->GetInternalField(kDataIndex)); npm error | ^ npm error 7 warnings and 3 errors generated. npm error make: *** [Release/obj.target/zmq/binding.o] Error 1 npm error gyp ERR! build error npm error gyp ERR! stack Error: `make` failed with exit code: 2 npm error gyp ERR! stack at ChildProcess.<anonymous> (/redacted/.nvm/versions/node/v22.9.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:216:23) npm error gyp ERR! System Darwin 24.2.0 npm error gyp ERR! command "/redacted/.nvm/versions/node/v22.9.0/bin/node" "/redacted/.nvm/versions/node/v22.9.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" npm error gyp ERR! cwd /redacted/node_modules/zeromq npm error gyp ERR! node -v v22.9.0 npm error gyp ERR! node-gyp -v v10.2.0 npm error gyp ERR! not ok
The text was updated successfully, but these errors were encountered:
Error comes from the zeromq@^5.0.0 dependency. Getting rid of it would mean refactoring to zeromq@6
Related: zeromq/zeromq.js#591 zeromq/zeromq.js#592
Sorry, something went wrong.
No branches or pull requests
Error of
The text was updated successfully, but these errors were encountered: