-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Fix streaming in Node.js fast path #11058
Conversation
🦋 Changeset detectedLatest commit: 848a3dc The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
!preview node-streaming |
Snapshots have been released for the following packages:
Publish Log
Build Log
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks right to me! Unsure if the renderingComplete
is needed, since I'd assume next()
won't be triggered again if rendering has completed. But I don't know the wider context.
@bholmesdev i'll add a comment explaining why it's needed. |
Changes
Testing
Docs
N/A, bug fix