WASM issue using dotnet-serve

[houstonhaynes]

Describe the bug

FYI - I'm running into an issue with dotnet serve per the instructions. This is confirmed when running dotnet-serve on either Windows or Linux - I get a "nice clean" console in the browser with no issues but the screen is simply blank after loading (the index.html pre-load/splash page loads as expected).

Running locally from JetBrains Rider or dotnet run from the command line is fine, BTW. It's only when serving from the AppBundle

Avalonia 11.1.0
dotnet sdk 8.0.4

To Reproduce

dotnet publish -p:CompressionEnabled=false 
dotnet serve -d:./bin/Release/net8.0-browser/browser-wasm/AppBundle --port 5000 --address any 

Expected behavior

load of WASM page in browser

Avalonia version

11.1.0

OS

Windows, Linux, WebAssembly

Additional context

running from command line dotnet run is fine.

[maxkatz6]

I just updated documentation to mention correct dotnet publish output path used in dotnet serve
https://docs.avaloniaui.net/docs/guides/platforms/how-to-use-web-assembly#deployment

Also tried to reproduce this problem with correct output path, but couldn't.
If it's still reproducible for you, can you attach a minimal repro?

[houstonhaynes]

Thanks so much for looking into this. We had to go to SAFEr stack for the primary web interface, but I may still use Avalonia for the admin console. If anything, it will be a valid exercise for deployment in the cloudflare pages, which we still have to sort out for this particular client.