fix: remove tower service if wasm32

[gusinacio]

No description provided.

[eopb]

Please can you provide more details around what's not working when the target is wasm?

I'd like to understand this before merging. Please also update the changelog.

[podusowski]

Hi,
I haven't had a change to look at it deeper, but I too got problem with building reqwest-middleware on WASM since 0.3. I suppose I could, and maybe even should just not use reqwest-middleware on WASM as in my case it's for HTTP caching, but I thought you might want to know.

https://github.com/podusowski/walkers/actions/runs/11654418524/job/32447924794?pr=220

[nickguletskii]

@eopb Without this patch, builds for wasm32-unknown-unknown fail with the following errors:

error[E0599]: no method named `poll_ready` found for struct `Client` in the current scope
   --> reqwest-middleware/src/client.rs:284:24
    |
284 |             self.inner.poll_ready(cx).map_err(crate::Error::Reqwest)
    |                        ^^^^^^^^^^ method not found in `Client`

error[E0599]: no method named `poll_ready` found for reference `&Client` in the current scope
   --> reqwest-middleware/src/client.rs:306:27
    |
306 |             (&self.inner).poll_ready(cx).map_err(crate::Error::Reqwest)
    |                           ^^^^^^^^^^ method not found in `&Client`

error[E0599]: no method named `timeout` found for struct `reqwest::RequestBuilder` in the current scope
   --> reqwest-middleware/src/client.rs:427:31
    |
427 |             inner: self.inner.timeout(timeout),
    |                               ^^^^^^^ method not found in `RequestBuilder`

For more information about this error, try `rustc --explain E0599`.

You can reproduce this issue by running cargo build --target wasm32-unknown-unknown.

[eopb]

I see. Thanks for the information everyone.

Looking back at the git history, wasm has been somewhat unmaintained in reqwest-middleware for a while. We removed the tests for wasm in #105.

I'd be happy to merge this but ideally, someone should also add back some of tests so that we can ensure that we don't regress this fix in a future change. At the very least we should check in CI that the library builds with the wasm target.