Vite 6.0.11 breaks fresh Laravel installations (custom domains with herd)

[WesWeCan]

Describe the bug

Checking the last release it is clear that something changed in the way CORS are handled in vite.

3d03899

is there a way to properly handle these changes?

Reproduction

Steps to reproduce

Create a new laravel app, use herd for the .test domains

I used a starterkit with vue, fresh out of the box

yarn dev

System Info

System:
    OS: macOS 15.2
    CPU: (16) arm64 Apple M3 Max
    Memory: 16.13 GB / 128.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Yarn: 1.22.22 - ~/Library/Application Support/Herd/config/nvm/versions/node/v22.13.0/bin/yarn
    npm: 11.0.0 - ~/Library/Application Support/Herd/config/nvm/versions/node/v22.13.0/bin/npm
  Browsers:
    Chrome: 131.0.6778.265
    Safari: 18.2
  npmPackages:
    @vitejs/plugin-vue: ^5.0.0 => 5.2.1 
    vite: ^6 => 6.0.11

Used Package Manager

yarn

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• 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.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.