-
Notifications
You must be signed in to change notification settings - Fork 198
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
HTML streaming not working with Remix app #966
Comments
👋 Thanks for the report. You're correct, the preview window does not properly stream the response back. This is something we haven't got around implementing. We're tracking this internally now (thanks!). |
@jrvidal I also couldn't get streaming to work when I opened the preview window in a new tab btw |
Yes, that is expected 👍 It's an issue with our networking stack. |
Chiming in with sveltejs/learn.svelte.dev#352, so that the issues are linked on GitHub! This is currently blocking us from documenting streaming behaviour on learn.svelte.dev, unfortunately |
Hey everyone! We have added initial support for HTTP streaming! 🎉 @tom-sherman, I have tested your example and we can now see @Rich-Harris, I've tested your PR and it also works! I'll be on the lookout for performance regressions, so if you notice anything please let me know! 😃 |
Describe the bug
When I run this locally, page is rendered as HTML with the suspense boundary as "Loading..." then the promise resolves on the server and is streamed to the client, and the "Loading..." changes to "Hello World".
On stackblitz though, no data is sent until the entire response is done (and so you see no "Loading..." state)
Link to the blitz that caused the error
https://stackblitz.com/edit/remix-starter-updated-t1fani?file=app%2Froutes%2Findex.tsx,app%2Fentry.server.tsx
Steps to reproduce
Expected behavior
See a Loading... message, and then this changes to "Data: Hello World"
Parity with Local
Screenshots
No response
Platform
Additional context
No response
The text was updated successfully, but these errors were encountered: