Fix:vitejs#5265 Add disableDotRule option to allow path contains dot

[gauntiantian]

Description

Additional context

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[Shinigami92]

I'm not sure if this is the right solution 🤔

[Niputi]

please correct title with (fix) and add a description telling which issue this will fix and why you believe this is the correct way to fix the issue

[bluwy]

I don't see what this solves either. @gauntiantian Can you provide some context as to why this is needed?

[gauntiantian]

check it out
https://www.npmjs.com/package/connect-history-api-fallback

[Niputi]

please provide tests for this and give more of an explanation than just a link

[David-Mueller]

Hi,
I guess I would benefit from this as well.

If route parameters of a vue app include dots (like a JWT), the route param won't be matched by Vite's dev server.
There was a "disableDotRule" option in webpack dev server to get around that as well: https://webpack.js.org/configuration/dev-server/#devserverhistoryapifallback

[andreas-ateles]

I need this in my project as well.

For example to display file information about a file in the app, an URL like this is used: example.com/file-info/some/path/to/file.txt

Currently the Vite dev server 404s when such URLs with a dot are loaded.

What do we need to do to get this merged?

[sapphi-red]

This is a duplicate of #2634. Closing this PR as #2634 includes more information.