How To Detect Unsupported Browsers Under a Blazor WebAssembly Application?

I recently ran into an issue where running a Blazor WebAssembly application under unsupported browsers would simply get stuck on the loading page. Whereas older browsers are supported under the “Server Side” model, it would be a much better experience to present the user with a more meaningful indicator that the browser is not supported when running “Blazor WebAssembly” model. Currently, when running Blazor WebAssembly under older browsers you get a loading indicator that never materializes to a page.