-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
allow turning off tonic_build transport feature for wasm target alone #1538
Comments
Is this issue still relevant? Is using tonic while targeting wasm possible today? |
I disabled [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"] } |
@borngraced Great that it works for you. I still have the problem, but thanks for the idea. 😀 |
What's the problem?..be specific please |
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. |
this would be useful for using tonic with
WASM
The text was updated successfully, but these errors were encountered: