-
Notifications
You must be signed in to change notification settings - Fork 49.3k
[Flight] Build Node.js Web Streams builds for Turbopack and Parcel #33457
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
Conversation
49bc9e2
to
5449539
Compare
5449539
to
aaa95aa
Compare
}; | ||
exports.createServerReference = function (i, c, e, d, f) { | ||
return w.registerServerReference( | ||
n.createServerReference(i, c, e, d, f), |
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.
Only id
and exportName
are expected here, I think.
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.
Same answer
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.
This one's a bit different than the others though, because the second arg is actually exportName
, and not callServer
. Doesn't matter at runtime right now, but it's at least confusing.
Reverts #33457, #33456 and #33442. There are too many issues with wrappers, lazy init, stateful modules, duplicate instantiation of async_hooks and duplication of code. Instead, we'll just do a wrapper polyfill that uses Node Streams internally. I kept the client indirection files that I added for consistency with the server though.
Same as #33456 and #33442 but for Turbopack and Parcel.