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
On local dev server vite will overeagerly return 404 if there is just one path fragment and it contains a period, e.g. "/example.com". I'm guessing that this is because of the path parsing logic deciding that the fragment looks like something that should be served by the filesystem.
Reproduction
Try accessing /examplecom on the vanilla dev server - things work as expected, the path is intercepted and passed to the browser (no effect)
Now try accessing /example.com - you'll get a 404
Note that adding a trailing slash /example.com/ will once again work.
Before submitting the issue, please make sure you do the following
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Provide a description in this issue that describes the bug.
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 https://github.com/vuejs/vue-next instead.
Describe the bug
On local dev server vite will overeagerly return 404 if there is just one path fragment and it contains a period, e.g. "/example.com". I'm guessing that this is because of the path parsing logic deciding that the fragment looks like something that should be served by the filesystem.
Reproduction
/examplecom
on the vanilla dev server - things work as expected, the path is intercepted and passed to the browser (no effect)/example.com
- you'll get a 404Note that adding a trailing slash
/example.com/
will once again work.Before submitting the issue, please make sure you do the following
The text was updated successfully, but these errors were encountered: