We need to validate that a substreams transformation module with target wasm32-unknown-unknown will be compiled WITHOUT the wasi extensions, even if our crate contains OPTIONAL (in sub-packages like server) code that would compile those wasi_snapshot-preview.fd_write methods). The goal is to have a SINGLE crate called substreams-sink-kv, but that we could use from within substreams modules (when doing transforms), AS WELL as in the KV Sink's inject/serve modes,, which is a totally different Wasm environment. Substreams compilation needs to ignore that server package.
We need to validate that a substreams transformation module with target wasm32-unknown-unknown will be compiled WITHOUT the wasi extensions, even if our crate contains OPTIONAL (in sub-packages like server) code that would compile those wasi_snapshot-preview.fd_write methods). The goal is to have a SINGLE crate called substreams-sink-kv, but that we could use from within substreams modules (when doing transforms), AS WELL as in the KV Sink's inject/serve modes,, which is a totally different Wasm environment. Substreams compilation needs to ignore that server package.