-
-
Notifications
You must be signed in to change notification settings - Fork 4
renderToPipeableStream in server.js Does Not Wait for Async Content Inside Suspense #40
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
Comments
Thank you for submitting this issue! We, the Members of Meteor Community Packages take every issue seriously. However, we contribute to these packages mostly in our free time. If you think this issue is trivial to solve, don't hesitate to submit Please also consider sponsoring the maintainers of the package. |
I think the issue you are seeing is that the |
@copleykj I tried it, but it still doesn’t work. Here’s a reproducible fork link (https://github.com/welkinwong/react-router-ssr-demo-issue), just upgraded to [email protected]. |
Thanks, I'll have a look. |
The
renderToString
method inserver.js
converts the stream returned byrenderToPipeableStream
into a string. However, during testing, it was observed that onAllReady is triggered andtoString()
is called before the stream fully completes, meaning it does not wait for asynchronous content inside Suspense boundaries.Issue:
Reproduction Steps:
In this project: https://github.com/copleykj/react-router-ssr-demo
upgrade
react-meteor-data
to[email protected]
, and the issue can be observed.PS: I used a
loggerStream
to log chunk information for debugging.In the forums, users reported a failure in
[email protected]
https://forums.meteor.com/t/communitypackages-react-router-ssr-v6-beta-release/63418/3
The text was updated successfully, but these errors were encountered: