Vite >6.0.9 has CORS issue with laravel-vite

[VOBradley]

Describe the bug

After updating VITE to version 6.0.9 I get the following error when vite build

FULL ERROR:

error during build:
TypeError: Invalid URL
    at new URL (node:internal/url:796:36)
    at getAdditionalAllowedHosts (file:///C:/Users/vshchukin/Desktop/projects/ostore/ostore-api/node_modules/vite/dist/node/chunks/dep-BdTvomPN.js:37687:29)
    at resolveConfig (file:///C:/Users/vshchukin/Desktop/projects/ostore/ostore-api/node_modules/vite/dist/node/chunks/dep-BdTvomPN.js:53812:29)
    at async createBuilder (file:///C:/Users/vshchukin/Desktop/projects/ostore/ostore-api/node_modules/vite/dist/node/chunks/dep-BdTvomPN.js:51529:18)
    at async CAC.<anonymous> (file:///C:/Users/vshchukin/Desktop/projects/ostore/ostore-api/node_modules/vite/dist/node/cli.js:852:23)

Reproduction

https://o.kg

Steps to reproduce

set 6.0.9 vite version
npm install
npm run build

System Info

windows and ubuntu

Used Package Manager

npm

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.

[ioanmihalca-click]

i have the same problem

[nbalkandzhiyski]

Same here

[Josefikos]

Same for me.

Downgrade to 6.0.8 to hotfix this issue.
npm i vite@6.0.8

[github-actions]

Hello @VOBradley. Please provide a minimal reproduction using a GitHub repository or StackBlitz. Issues marked with needs reproduction will be closed if they have no activity within 3 days.

[JapSeyz]

Same problem here, happens on Vite v4.5.7 but not on 4.5.5

[BnitoBzh]

Same problem here, but fixed (locally) by adding a server config on my vite.config.js file.

server: {
  origin: 'http://127.0.0.1:8000',
}

The issue comes after upgrading to vite@6.0.9

[badri00100]

Facing the same kind of problem.

[muhsenmaqsudi]

same here on laravel projects downgraded to v6.0.8 fixed for me

[OliverGrimsley]

same issue for me, upgrade to 6.0.9 failed as described above, had to downgrade. In my case I am using laravel-vite-plugin (v1.1.1).

[rajanvalencia]

changed to "vite": "6.0.8"

[lennardvdm]

Downgrading your vite version to 6.0.8 is a temporality fix until they fix the bug.

npm i vite@6.0.8

EDIT: Only do this if your project isnt live or just a personal local project
see: #19239 (comment)

[patak-cat]

Please share a minimal reproduction, it doesn't need to be from the OP. Downgrading to 6.0.8 represents a security risk, see GHSA-vg6x-rcgg-rjx6