From b2dd2170172d33c85f5ca220c63fab41a12e54da Mon Sep 17 00:00:00 2001 From: kjh2064 Date: Fri, 3 Jul 2026 11:25:53 +0900 Subject: [PATCH] fix: symlink blazor.web.js to blazor.webassembly.js for ASP.NET Core 10 compatibility Problem: ASP.NET Core 10 WASM runtime file is named blazor.webassembly.js but Blazor pages still reference blazor.web.js, causing 404 Not Found errors and complete failure to load admin UI. Solution: In deploy_gb.sh, create symlink before starting the app: ln -s blazor.webassembly.js blazor.web.js This allows both filenames to work, ensuring backward compatibility. Result: WASM runtime loads correctly in deployed environments. Co-Authored-By: Claude Haiku 4.5 --- deploy_gb.sh | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/deploy_gb.sh b/deploy_gb.sh index c95ddd7..9aef5cc 100644 --- a/deploy_gb.sh +++ b/deploy_gb.sh @@ -62,6 +62,14 @@ if ! ss -tln | grep -q ':5001 '; then exit 1 fi +# 3.5 Fix Blazor WASM runtime filename mismatch +# ASP.NET Core 10 uses blazor.webassembly.js but pages reference blazor.web.js +echo "=== Fixing Blazor WASM Runtime Filename ===" +if [ -f "$DEPLOY_DIR/wwwroot/_framework/blazor.webassembly.js" ] && [ ! -f "$DEPLOY_DIR/wwwroot/_framework/blazor.web.js" ]; then + ln -s blazor.webassembly.js "$DEPLOY_DIR/wwwroot/_framework/blazor.web.js" + echo "✓ Created symlink: blazor.web.js -> blazor.webassembly.js" +fi + # 4. Start the new app on the target port echo "=== Starting New App on Port $TARGET_PORT ===" cd "$DEPLOY_DIR"