Blazor routing struggles across static hosts and nested components
Blazor developers need URL navigation to work in environments where the host cannot rewrite arbitrary paths to the app’s index page, and want routing that goes beyond page-level components. Static CDN, Chrome extension, and nested GitHub Pages deployments are cited as troublesome; one workaround is rewriting requests to index.html, while nested component flows can require a large root-level switch. A separate request about rendering Razor pages in Blazor Server is adjacent app-composition friction, but is not clearly the same core problem.
For blazor WebAssembly and Server developers. Mentioned from Feb 2020 to Mar 2022 on GitHub.
6 different people described this problem in 3 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 5.7/10
- Frequency
- 7.0/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
We ran into this same issue hosting a static Blazor SPA on a CDN. All status code have to redirect back to index.html
I'm trying to use Blazor WASM inside a Chrome extension and I can't reroute all requests to index.html. Hash routing would be helpful
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 4 more quotes from people who have this problem
- Current workarounds, existing solutions and risks