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
{{ message }}
This repository has been archived by the owner on Aug 11, 2021. It is now read-only.
Currently, this module brings in a Native dep sha3@1.2.0. Would it be possible to move to js-sha3, the same used in js-multihashing-async, so that it doesn't represent a blocker for js-ipfs electron users
> fsevents@1.1.2 install /Users/koruza/code/js-ipld-eth-star/node_modules/fsevents
> node install
[fsevents] Success: "/Users/koruza/code/js-ipld-eth-star/node_modules/fsevents/lib/binding/Release/node-v51-darwin-x64/fse.node" is installed via remote
> sha3@1.2.0 install /Users/koruza/code/js-ipld-eth-star/node_modules/sha3
> node-gyp rebuild
CXX(target) Release/obj.target/sha3/src/addon.o
../src/addon.cpp:59:36: warning: 'NewInstance' is deprecated [-Wdeprecated-declarations]
info.GetReturnValue().Set(cons->NewInstance(argc, argv));
^
/Users/koruza/.node-gyp/7.10.0/include/node/v8.h:3658:31: note: 'NewInstance' has been explicitly marked deprecated
here
Local<Object> NewInstance(int argc, Local<Value> argv[]) const);
^
1 warning generated.
CXX(target) Release/obj.target/sha3/src/displayIntermediateValues.o
CXX(target) Release/obj.target/sha3/src/KeccakF-1600-reference.o
CXX(target) Release/obj.target/sha3/src/KeccakNISTInterface.o
CXX(target) Release/obj.target/sha3/src/KeccakSponge.o
SOLINK_MODULE(target) Release/sha3.node
> keccak@1.3.0 install /Users/koruza/code/js-ipld-eth-star/node_modules/keccak
> prebuild-install || node-gyp rebuild || echo "Keccak bindings compilation fail. Pure JS implementation will be used."
Thanks!
The text was updated successfully, but these errors were encountered:
daviddias
changed the title
Any change of moving to js-sha3?
Any chance of moving to js-sha3?
Aug 25, 2017
@diasdavid This is set up so that you get the js implementation when targeting the browser, and c++ on node (with failover to js). So is there some error with the failover when targeting electron?
I'm still investigating, but as far as I understand electron-rebuild is not super friendly to deps in Node.js that fail. It doesn't work well with the failover.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, this module brings in a Native dep
sha3@1.2.0
. Would it be possible to move tojs-sha3
, the same used injs-multihashing-async
, so that it doesn't represent a blocker for js-ipfs electron usersThanks!
The text was updated successfully, but these errors were encountered: