Vite plugin not serving assets in SPA mode

[farnoy]

What versions & operating system are you using?

wrangler 4.14.1 vite-plugin 1.7.5 node 22.14

Please provide a link to a minimal reproduction

No response

Describe the Bug

I'm trying to move from running wrangler and vite separately from my SPA + API app but with the new vite plugin, only the root path / or /index.html work, all other routes like /example get 404s from the dev server. This mode with run_worker_first=false and not_found_handling=single-page-application works when deployed to CF, it only affects the vite plugin

Please provide any relevant error logs

No response

[jamesopstad]

Are you able to provide a reproduction and could you confirm if you are developing on localhost or a different host? Thanks.

[farnoy]

I am using __VITE_ADDITIONAL_SERVER_ALLOWED_HOSTS and --host 0.0.0.0. When testing it with curl it does seem to work. I think the problem is Chrome doesn't want to send the Sec-Fetch-Mode header to an HTTP server? 🤦

[farnoy]

Yep, that was it. I needed to add my host to chrome://flags/#unsafely-treat-insecure-origin-as-secure so it gets these headers

[jamesopstad]

Glad you resolved it. Another option is to opt in to explicit routing by setting run_worker_first to an array of routes that should invoke your Worker e.g. ["/api/*"]. This disables interpreting the sec-fetch-mode header.

[farnoy]

Of course, but then I'm paying for worker invocations on static asset serving, so I'd rather take the devex inconvenience 😄

[jamesopstad]

Only routes that match those in run_worker_first invoke your Worker so you wouldn't be charged differently.

[farnoy]

Oh I see what you mean. That's probably the cleanest solution.