kjh2064/taxbaik
1
0
Fork 0
Code Issues 1 Pull Requests Actions 2 Packages Projects Releases Wiki Activity

fix: symlink blazor.web.js to blazor.webassembly.js for ASP.NET Core 10 compatibility
TaxBaik CI/CD / build-and-deploy (push) Successful in 2m49s
Details

Browse Source 
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 <noreply@anthropic.com>
This commit is contained in:
김재현
2026-07-03 11:25:53 +09:00
parent e044acea17
commit b2dd217017
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
deploy_gb.sh
+8
View File
@@ -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"