Closed emidev98 closed 2 years ago
@motorina0 this sounds like fun...
It seems like the only way to "fix" this is to remove node based hashing and only use pure JS hashing.
Alternatively, we could also use WASM.
or actually this might be better fixed upstream: https://github.com/crypto-browserify/createHash
......? I looked at Node v17 API for createHash... it hasn't really changed...
Is it just that OpenSSL no longer supports ripemd160?
@motorina0 this sounds like fun...
yes, but you are too fast. Do you ever sleep?
Just to summarize:
v17
upgrading to OpenSSL 3.0
(from OpenSSL 1.1.1
). Reported also on other projects.--openssl-legacy-provider
flag (NODE_OPTIONS=--openssl-legacy-provider npm run test
)crypto.ts
):
const createHash = require('create-hash/browser');
Fixed in 3.1.0
Hello, we have found that the library has breaking changes with node v17. The reason why is explained in this webiste, but a tinny extract from the website says:
NPM/NodeJs:
Error:
Please let us know if more information is needed or if we can help on a different way