Build WASM Engine

Build the Bevy engine as WebAssembly for the browser. This produces 4 variants:

• engine-pkg-webgl2 — WebGL2 editor build
• engine-pkg-webgpu — WebGPU editor build
• engine-pkg-webgl2-runtime — WebGL2 game runtime (no editor features)
• engine-pkg-webgpu-runtime — WebGPU game runtime (no editor features)

Prerequisites

Verify these are available before building:

• rustc (stable)
• wasm32-unknown-unknown target installed (rustup target list --installed)
• wasm-bindgen CLI v0.2.127 (wasm-bindgen --version) — must match Cargo.lock

Build Steps

Full build (default when $ARGUMENTS is empty or "all")

Run the PowerShell build script from the project root:

# From project root:
powershell -ExecutionPolicy Bypass -File build_wasm.ps1

This handles:

1. Setting LIB env for Windows SDK (proc-macro native linking)
2. Building 4 cargo variants (webgl2, webgpu, webgl2 runtime, webgpu runtime)
3. Running wasm-bindgen on each
4. Optionally running wasm-opt -Oz for size reduction
5. Copying output to web/public/engine-pkg-*

Single variant build

If $ARGUMENTS is "webgl2" or "webgpu", build only that variant:

cd engine
cargo build --target wasm32-unknown-unknown --release --features $ARGUMENTS
wasm-bindgen --target web --out-dir pkg-$ARGUMENTS target/wasm32-unknown-unknown/release/forge_engine.wasm

Verification

After building, verify the output exists:

ls -la web/public/engine-pkg-webgl2/forge_engine_bg.wasm
ls -la web/public/engine-pkg-webgpu/forge_engine_bg.wasm

Common Issues

• wasm-bindgen version mismatch: Must be 0.2.127. Install with cargo install wasm-bindgen-cli --version 0.2.127
• Missing LIB env: Proc-macro crates (e.g., doc-image-embed) need Windows SDK libs for native host compilation
• Build time: Full build takes ~5-10 minutes depending on hardware

Lockfile Consistency

Verify package-lock.json is consistent with all package.json files. Run after cherry-picks, rebases, or manual package.json edits. A stale lockfile fails ALL CI jobs simultaneously (npm ci requires exact match).

Check for drift

cd "$(git rev-parse --show-toplevel)"
npm install --dry-run 2>&1 | grep -E "added|removed|changed"

If the dry-run shows changes, the lockfile is stale.

Fix stale lockfile

cd "$(git rev-parse --show-toplevel)"
npm install
git add package-lock.json
git commit -m "fix: regenerate lockfile after dependency changes"

When to run

• After git cherry-pick that touches any package.json
• After git rebase across commits that modified dependencies
• After manually editing any package.json