Name the profiles to not suggest they're WASM-only

A couple extra build profiles
Use wasm-server-runner as the WASM runner
2025-08-14 11:04:20 -05:00 · 2025-08-14 11:04:20 -05:00 · 2025-08-14 11:03:37 -05:00 · 2025-08-14 11:03:37 -05:00 · 2025-08-14 10:34:03 -05:00 · 2025-08-14 08:58:02 -05:00
2 changed files with 30 additions and 3 deletions
--- a/.cargo/config.toml
+++ b/.cargo/config.toml
@@ -0,0 +1,4 @@
+
+[target.wasm32-unknown-unknown]
+runner = "wasm-server-runner"
+rustflags = ["--cfg", "getrandom_backend=\"wasm_js\""]
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -1,10 +1,33 @@
 [package]
 name = "asteroids"
-version = "0.2.0"
+version = "0.3.0"
 edition = "2024"

 [dependencies]
-bevy = { version = "0.16", features = ["dynamic_linking"] }
+bevy = "0.16"
 bevy-inspector-egui = "0.32.0"
-bevy_rapier2d = { version = "0.31.0", features = ["debug-render-2d"] }
+bevy_rapier2d = "0.31.0"
 rand = "0.9.2"
+
+[features]
+dynamic_linking = ["bevy/dynamic_linking"]
+debug_ui = ["bevy_rapier2d/debug-render-2d"]
+
+[target.'cfg(target_arch = "wasm32")'.dependencies]
+getrandom = { version = "0.3.3", features = ["wasm_js"] }
+
+[profile.speedy]
+inherits = "release"
+codegen-units = 1
+lto = "fat"
+opt-level = 3
+strip = "symbols"
+panic = "abort"
+
+[profile.tiny]
+inherits = "release"
+codegen-units = 1
+lto = "fat"
+opt-level = "z"
+strip = "symbols"
+panic = "abort"
Author	SHA1	Message	Date
Robert Garrett	9d9b25d1df	Name the profiles to not suggest they're WASM-only All checks were successful Basic checks / Basic build-and-test supertask (push) Successful in 7m13s Details	2025-08-14 11:04:20 -05:00
Robert Garrett	89ee328807	A couple extra build profiles	2025-08-14 11:04:20 -05:00
Robert Garrett	90d8142855	Use `wasm-server-runner` as the WASM runner This way I can `cargo run --target ...` and Cargo will spawn a dummy webserver instead of attempting to execute the WASM file on my x86/arm CPU.	2025-08-14 11:03:37 -05:00
Robert Garrett	10366b642c	Add wasm-specific feature for RNG child dependency The `rand` crate eventually depends on `getrandom` which requires a different feature set when running in the browser. WASM has no OS, and so no RNG provider... but the browser, specifically, has one that the JavaScript runtime can touch. Enabling the "wasm_js" feature on `getrandom` allowes it to use this backend. An extra config option must also be passed to `rustc`. THis can be set through the environment, or the config.toml. I've chosen the latter so I don't need to think about it very often.	2025-08-14 11:03:37 -05:00
Robert Garrett	94e0cd0999	Add my own crate features to pass through to deps All checks were successful Basic checks / Basic build-and-test supertask (push) Successful in 7m25s Details Closes #20 Now this crate can be told to build with or without certain behavior, rather than needing to patch the Cargo.toml file.	2025-08-14 10:34:03 -05:00
Robert Garrett	18d026637b	Bump the crate version I marked 0.2 at some point, so I guess I should keep incrementing this during development. The menus are finished, which is as good a checkpoint as any.	2025-08-14 08:58:02 -05:00