-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Starting dev server for first time throws 408 timeouts on initial fetch to populate readable store - restart dev server and it goes away #1644
Comments
Same here, Windows and Mac. |
Same here, Linux. Doesn't solve it even with a restart. |
Just installed SvelteKit v1.0.0-next.146 and the problem (so far) has not reoccured. I believe this change:
@frederikhors and @manen - can you please upgrade SvelteKit to v.1.0.0-next.146 and see if the problem goes away for you as well? |
You need to restart many times! |
Gimme some hours... and I will let you know! |
I think that now I will cry with happiness. You can close this issue! |
I use the load function now, so for me it's solved. thanks though |
Solved by @sveltejs/kit@1.0.0-next.146. |
Environment
SvelteKit v1.0.0-next.144
Svelte 3.42.1
OS: macOS 11.5.1
Browser: Safari 14.1.2 and Chrome 92
Describe the bug
If I bump any dependencies then run
npm install && npm run dev -- --open
, I get HTTP 408 errors when my readable stores are created via GETs to my API (same project - not external). If I immediately do a Ctrl-C and restart the dev server, the errors go away.Logs (showing the errors then the errors going away after restarting dev server)
Here's the path it takes for the GET from /api/location/active.json...
Severity
Severity is medium because I can always Ctrl-C and restart the dev server but it might create an impression of instability in SvelteKit which is why I didn't mark this as low.
Perhaps the initial fetch is failing because something is still being initialized by SvelteKit and the dev server isn't really up and running?
The text was updated successfully, but these errors were encountered: