-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
asset load failure results in entire page broken #13519
Comments
More context: Locally just having not rendering root error page here kit/packages/kit/src/runtime/client/client.js Line 2580 in 3cf2b77
|
Could you provide an updated reproduction (the linked one is completely outdated and I don't know how to upgrade it to a place where the error is observable using current SvelteKit and Vite)? I'm having trouble to understand in which step exactly the error is occuring for you (the one you mentioned is about loading nodes, not doing the component rendering) Update: Ok I think I know what you mean - if loading one of the entry JS page nodes ( |
So, an easy way to reproduce is to I added hydrate = false;
return; here kit/packages/kit/src/runtime/client/client.js Line 2580 in 3cf2b77
|
Describe the bug
This is the same bug as reported in #2699
I am only opening a new one as the previous one was closed and might not get any traction. If you want to reopen the old one, feel free to close this as duplicate.
This is a real world problem any asset load failure during network fluctuation results in entire page broken even when the page is fully Server side rendered. This is a problem affecting real users, and we are really hoping to get this resolved for our Yahoo Finance users.
Proposal
Introduce an option in kit which when enabled, is going to catch such errors, so we don't show the default error page and atleast show the server side rendered markup.
Reproduction
https://github.com/benmccann/500-import-failure
Logs
System Info
Severity
blocking all usage of SvelteKit
Additional Information
No response
The text was updated successfully, but these errors were encountered: