Closed mark-ruddy closed 2 years ago
My bad this issue was unnecessary - just found the readme note about wasm
.
For anyone who finds this issue in a similar situation to get it to build add this to your Cargo.toml:
web3 = { version = "0.18.0", default_features = false, features = ["wasm"] }
15 | use web3::signing::{keccak256, recover};
| ^^^^^^^ no `recover` in `signing`
but in wasm, the signing has no recover
Hi - I'm not sure if it is a target of this crate to build for
wasm32-unknown-unknown
but in my experience most crates do build for this target without issue.If there was a simple update that would allow this crate to build for this target it would be great.
How to reproduce:
Short snippet of the large amount of error output, seems in general possibly a conflict with the
std::net
?: