`bitreq` doesn't support WASM transport

[luisschwab]

bitreq has no support for a WASM transport, breaking compatibility for bdk_esplora on WASM targets.

ref: bitcoindevkit/bdk#2189

[alexgrad42]

Hi All,

I would like to look into this issue and add WASM transport support to bitreq.

Since bitreq is a lightweight client with minimal dependencies, I wanted to double-check the approach.

What is better for the target_arch = "wasm32" implementation?

1. A manual implementation using raw browser APIs via web-sys / wasm-bindgen (Fetch API) to avoid adding high-level external dependencies.
2. Bringing in a lightweight, WASM-specific HTTP client (like gloo-net or a similar micro-crate) gated behind the wasm32 configuration flag.

Also, please let me know if exposing an async entry point for WASM is acceptable, or the existing transport design has specific constraints.

Thanks!

[tnull]

I think @tankyleo is already working on adding WASM support and has made some progress.