-
Notifications
You must be signed in to change notification settings - Fork 30
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
Node Fibers #7
Comments
Without changing React, no. |
Well... it can be possible but that would require several iterations per render: render once, collect all async components, fetch state, re-render, ... repeate until no async components is left. |
Got it! Thanks, that makes sense. |
what about ES6 generators? |
@wwwsevolod the same, React rendering doesn't yield. |
@andreypopp by the way, do you see any downsides in using fibers for this? |
@nickdima three things
|
@wwwsevolod it's the other way around, it was async but now it isn't anymore. Also because it wasn't a real async implementation. |
sorry, i misread this, deleted my message when understand this lol ;( |
Do you think it would be theoretically possible to implement
renderComponentToStringWithAsyncState
in a way that doens't usefibers
?The text was updated successfully, but these errors were encountered: