-
Notifications
You must be signed in to change notification settings - Fork 926
Node Stream support for react v18? #1265
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
Yeah I’m not sure the embedded v8 engine would support this at all with the
current architecture. Might need to revisit some
kind of real Node interop later, I believe there was a PR from a while ago
that explored making that work.
For now only string based rendering is supported, at least until we sort
that path out.
…On Thu, Sep 2, 2021 at 16:58, Loren Dorez ***@***.***> wrote:
With the upcoming React v18 i was wondering if much thought has been given
about how to implement Node streams. As some of the new features for v18
React.Lazy and React.Suspense will be leveraging a new nodestream
reactwg/react-18#22 <reactwg/react-18#22>
i dont have much experence on the node side of this. im not sure where to
start with a basic implementation using renderToNodeStream any guidance
would be appreciated.
I though about trying to do something with Web sockets and tie into the JS
Engines that way but not sure that would work.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1265>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHGCFVHDQPOH3TZQSNHO4DT77QPLANCNFSM5DJ6FDBQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Well I see JES has a node engine that could be used but again not sure how you would be able to wireup the cross talk between JSE <> .Net <> Client. I was thinking you could use websockets or signalR to help with the .Net <> Client but not sure the JSE can handle the constant connection between it and .Net |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the upcoming React v18 i was wondering if much thought has been given about how to implement Node streams. As some of the new features for v18 React.Lazy and React.Suspense will be leveraging a new nodestream reactwg/react-18#22
i dont have much experence on the node side of this. im not sure where to start with a basic implementation using
renderToNodeStream
any guidance would be appreciated.I though about trying to do something with Web sockets and tie into the JS Engines that way but not sure that would work.
The text was updated successfully, but these errors were encountered: