Conflicting imports of wasi cause wasm-component-ld error.

[cdmurph32]

Conflicting version of wasi will cause builds to crash. As more common crates are importing wasi this problem will grow if not addressed. In my particular case newer version of tempfile and uuid depended on a newer version of getrandom which depended on v0.13.3+wasi-0.2.2. This conflicted with my crate's direct dependency and the dependency of wstd on v0.14.1+wasi-0.2.3.

working_tree.txt

not_working_tree.txt

conflicting_wasi_error.txt

[alexcrichton]

It's hard to say without a reproduction, but my gut is that this is likely a duplicate of https://github.com/bytecodealliance/wasm-tools/issues/1897 and is also similar to https://github.com/bytecodealliance/wasm-component-ld/issues/52

[cdmurph32]

Reproduction steps:

1. Checkout https://github.com/contentauth/c2pa-rs/tree/wasm32-wasi_0.41.0
2. Change version of tempfile to v3.16.0
3. Run cargo +nightly build --target wasm32-wasip2 -p c2pa