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
In dev mode, the server is supposed to set Access-Control-Allow-Origin: * on every request. This is the case for some older versions of SvelteKit, like 1.0.0-next.193. However, in new versions, this header is omitted on static assets.
Reproduction
$ npm create svelte@latest my-app
create-svelte version 2.0.0-next.190
Welcome to SvelteKit!
This is release candidate software; expect bugs and missing features.
Problems? Open an issue on https://github.com/sveltejs/kit/issues if none exists already.
✔ Which Svelte app template? › SvelteKit demo app
✔ Add type checking with TypeScript? › Yes, using TypeScript syntax
✔ Add ESLint for code linting? … No / Yes
✔ Add Prettier for code formatting? … No / Yes
✔ Add Playwright for browser testing? … No / Yes
[... snip ...]
$ cd my-app
$ npm install && npm run dev
VITE v3.2.3 ready in 737 ms
➜ Local: http://localhost:5176/
➜ Network: use --host to expose
Describe the bug
In dev mode, the server is supposed to set
Access-Control-Allow-Origin: *
on every request. This is the case for some older versions of SvelteKit, like1.0.0-next.193
. However, in new versions, this header is omitted on static assets.Reproduction
Then, in other window:
Logs
No response
System Info
Severity
blocking an upgrade
Additional Information
No response
The text was updated successfully, but these errors were encountered: