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 #6550 we started simulating CORS errors for server-side fetches to avoid a discrepancy between server-side and client-side fetches.
More recently, in #7113, we added fetch to RequestEvent, meaning that you can use event.fetch in a +page.server.js or +layout.server.js. But the simulated CORS errors still apply, needlessly.
Describe the bug
In #6550 we started simulating CORS errors for server-side fetches to avoid a discrepancy between server-side and client-side fetches.
More recently, in #7113, we added
fetch
toRequestEvent
, meaning that you can useevent.fetch
in a+page.server.js
or+layout.server.js
. But the simulated CORS errors still apply, needlessly.Reproduction
https://github.com/Rich-Harris/sveltekit-server-side-fetch-bug-repro
Logs
No response
System Info
Severity
serious, but I can work around it
Additional Information
No response
The text was updated successfully, but these errors were encountered: