Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add FallbackToFile options for serving apps with client-side routing.
See original GitHub issueI have a react+typescript app use the React BrowserRouter.
For example, if I used React Router with a route for /todos , dotnet-serve will response a HTTP 404 .
This is because when there is a fresh page load for a /todos, the dotnet-server looks for the file build/todos{.html/htm} and does not find it. The dotnet-server should to be configured to respond to a request to /todos by serving index.html.
Describe the solution you’d like
Add options to configure FallbackToFile(...) endpoints. Such as :
dotnet serve --fallback-to-file "index.html"
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ok, I see what you are saying now. It sounds like you want all unknown routes to redirect to some default file. This behavior doesn’t seem to me to be like a common use case. I don’t plan to implement this, but I will leave this request open in case I am missing something.
Other users - please upvote if you want support for this feature request.
Released in https://github.com/natemcmaster/dotnet-serve/releases/tag/v1.10.155