Cem Eliguzel

Thanks @MarkusEicher and @thomastaylor312 . Having previously looked into the matter, I wanted to offer my insights in the hopes that they might be of assistance to you, @MarkusEicher.

Just to double check: Is the assumption that `cargo build --no-default-features` should succeed correct? The only dependent of the `wash-lib` is the `wash-cli` crate and it uses `default features +...

There seems to be 3 feature flags which cause this problem: `async-nats`, `serde` and `serde_json`. Should any of them by any chance be part of the `no-default-features` set? If not,...

Thanks for the explanation @thomastaylor312 @brooksmtownsend . Apparently, async_nats Client is used as the only means for the RPC connection without an alternative. Does it make sense to disable it...

@brooksmtownsend the following changes remove the build problem but I am not sure if it makes sense. Any opinion? ``` index a9597ce5..07f56f83 100644 --- a/crates/wash-lib/src/lib.rs +++ b/crates/wash-lib/src/lib.rs @@ -28,14 +28,21...

I have created a candidate solution for this.

Kindly reminder