fix: use wasm32v1-none target in getting-started.sh script

The wasm32-unknown-unknown target combined with the serde_core fork causes duplicate lang item errors. Using wasm32v1-none avoids the -Z build-std fallback that triggers the conflict.
2026-02-23 11:16:54 +03:00
parent 83e29dba8c
commit 1b38c0919e
1 changed files with 1 additions and 1 deletions
@@ -149,7 +149,7 @@ if prompt_default_yes "\n🦀 Setup the Rust environment (e.g. WASM support)?";
    printf "🦀 Setting up Rust environment.\n"
    rustup default stable
    rustup update
-    rustup target add wasm32-unknown-unknown
+    rustup target add wasm32v1-none
    rustup component add rust-src
 fi