getrandom v0.2.15 blocks uuid and compiling to wasm

[Wehzie]

What problem does this solve or what need does it fill?

Hey! I'm trying to build my bevy game for wasm32-unknown-unknown. When compiling for wasm I receive uuid couldn't build errors with could not find RngImp in imp in uuid-1.13.1/src/rng.rs:10:10. Cargo.lock has dependencies on getrandom 0.2.15 and 0.3.1. I had manually set getrandom = { version = "0.3", features = ["wasm_js"] } after following up on previous errors. I also set rustflags = ["--cfg", "getrandom_backend=\"wasm_js\""] in .cargo/config.toml.
Specifying the feature = ["wasm_js"] also requires specifying a version, setting version to "*" doesn't solve the issue either.

Following the dependency tree, the origin of these problems seems to be from bevy_utils on ahash on const-random on const-random-macro on getrandom.

getrandom v0.2.15
└── const-random-macro v0.1.16 (proc-macro)
    └── const-random v0.1.18
        └── ahash v0.8.11
            ├── bevy_utils v0.15.1
            │   ├── bevy_animation v0.15.1
            │   │   ├── bevy_gltf v0.15.1
            │   │   │   └── bevy_internal v0.15.1
            │   │   │       └── bevy v0.15.1



getrandom v0.2.15
├── ahash v0.8.11 (*)
└── rand_core v0.6.4
    ├── rand v0.8.5
    │   ├── bevy_math v0.15.1 (*)


also dependent on ahash v0.8.11:
      └── hashbrown v0.14.5
          └── bevy_utils v0.15.1 (*)

Maybe I'm on the completely wrong trail as desktop cargo run builds fine.

What solution would you like?

It seems that ahash and const-random-macro are updated only sporadically. Forking the packages to improve control over dependencies could be a solution.

What alternative(s) have you considered?

Other, more actively maintained dependencies could replace the packages in question.

Other

• OS: Ubuntu 24.10
• bevy 0.15.1
• rustup 1.27.1
• rustc 1.83.0

[bushrat011899]

As a workaround, can you try adding the following to you Cargo.toml:

[target.'cfg(target_arch = "wasm32")'.dependencies]
uuid = { version = "1.13.1", default-features = false, features = ["js"] }

This enables the js feature in uuid which should resolve the issues you're experiencing.

[simbleau]

We also just started getting this today - Screwing up our entire pipeline atm.

As a workaround, can you try adding the following to you Cargo.toml:

[target.'cfg(target_arch = "wasm32")'.dependencies]
uuid = { version = "1.13.1", default-features = false, features = ["js"] }

This enables the js feature in uuid which should resolve the issues you're experiencing.

Note for anyone who comes across this, this may not be enough.

You may also need to add this to a .cargo/config.toml:

[target.'cfg(target_family = "wasm")']
rustflags = ['--cfg=getrandom_backend="wasm_js"']

[Wehzie]

Thank you the fix works. To summarize,

my Cargo.toml looks as follows

[dependencies]
bevy = "0.15.1"
rand = "0.9.0"
getrandom = { version = "0.3", features = ["wasm_js"] }

[target.'cfg(target_arch = "wasm32")'.dependencies]
uuid = { version = "1.13.1", default-features = false, features = ["js"] }

and .cargo/config.toml

[target.'cfg(target_family = "wasm")']
runner = "wasm-server-runner"
rustflags = ['--cfg=getrandom_backend="wasm_js"']

[mockersf]

this should be fixed with the update to Bevy 0.15.2