Please consider making wasm dependencies target-specific for wasm targets

Rather than having a feature to enable to work on wasm, and then erroring out on wasm targets if that feature isn't enabled, please consider making those dependencies target-specific instead (or in addition), so that it never gets pulled in on non-wasm targets.

Inspect the Rust dependency and feature declarations, likely in the project manifest, and compare how dependencies are selected for wasm and non-wasm targets. Verify that wasm-only dependencies are not pulled into non-wasm builds and that wasm builds still work without requiring an extra feature.

Written by the indexing model from the issue text.