With the sample blazor wasm app downloaded from jamstacks.net I can’t hit the api endpoints via the browser; they all fallback to a page not found on index.html.
What is the best practice for preventing this behaviour?
Is it possible to host the api on a different port?
But this isn’t the case when running from localhost which should call your APIs when they exist, as-is required for the template to function. Are you saying you can’t call server routes? e.g:
The MyApp host project is the .NET server project which hosts the client WASM UI, whereas running the client project just runs the UI sans .NET Server APIs.
Not related, you should always run the MyApp Server project if your client needs it.
Hot reload with Blazor WASM is a mixed bag which sporadically works, usually works when you first open your project then stops working for me a bit later. The Hot Reload in Blazor Server provides a much nicer dev UX.