You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With a react-ts vite template, while running with the vite dev server, I had an app with routes like /sites/example.com or /sites/example.net (domain name shaped in my case, but I think anything abc.xyz would trigger this behavior) fail with 404. Client side routing was OK, but as soon I refreshed the browser on one of these paths, the vite dev server would load the page as a 404 and show nothing. For other routes, this did not happen.
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
Describe the bug
With a
react-ts
vite template, while running with the vite dev server, I had an app with routes like/sites/example.com
or/sites/example.net
(domain name shaped in my case, but I think anythingabc.xyz
would trigger this behavior) fail with 404. Client side routing was OK, but as soon I refreshed the browser on one of these paths, the vite dev server would load the page as a 404 and show nothing. For other routes, this did not happen.Here's a short video showing the bug.
This issue from a couple years ago is definitely related.
Reproduction
https://github.com/ryanmr/vite-404-example
Steps to reproduce
yarn create vite --template react-ts
/ cd / installApp.tsx
create a:yarn dev
System Info
Used Package Manager
yarn
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: