allow turning off tonic_build transport feature for wasm target alone

[borngraced]

this would be useful for using tonic with WASM

[tbmreza]

Is this issue still relevant? Is using tonic while targeting wasm possible today?

[borngraced]

I disabled transport feature and implemented in my code no need to rely on tonic_build for it

[target.'cfg(not(target_arch = "wasm32"))'.dependencies]
tonic = { version = "0.7", features = ["tls", "tls-webpki-roots", "compression"] }

[target.'cfg(target_arch = "wasm32")'.dependencies]
tonic = { version = "0.7", default-features = false, features = ["prost", "codegen", "compression"] }

[build-dependencies]
tonic-build = { version = "0.7", default-features = false, features = ["prost", "compression"] }

[tbmreza]

@borngraced Great that it works for you. I still have the problem, but thanks for the idea. 😀

[borngraced]

What's the problem?..be specific please

[tbmreza]

It's a runtime error (cargo c and cargo build are green using your config values) that I haven't figured out what the cause is. I have tried dioxus and trunk, same results.

[zoechi]

This is killing me. When I want to build for non-WASM I have to add the transport feature, when I want to build for WASM, I need to remove it. I wasn't able to find a way to configure dependencies so that it builds for both without manual intervention.

Perhaps I'm missing something, but when I add tonic-build as build-dependency twice, once without transport for no specific target and once with transport for all targets except WASM, Cargo unifies both and always uses transport independent of the target. (Edition 2024 with resolver 3)

My ugly hack for now is to add a non_wasm feature to enable transport

Some more details https://users.rust-lang.org/t/enable-dependency-feature-only-when-not-wasm/128980/9