-
Notifications
You must be signed in to change notification settings - Fork 28.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
http: expose websocket in nodehttp #53721
http: expose websocket in nodehttp #53721
Conversation
Review requested:
|
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.
Good job! Docs are missing too.
Can you add a test that the given objects are the same of the global?
I've added |
Co-authored-by: Aviv Keller <38299977+RedYetiDev@users.noreply.github.com>
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 good, just needs some documentation, but from (mostly, except minor changes) here-on-out, I'll leave the reviewing to collaborators.
Thank you @anfibiacreativa for implementing this so darn fast! 🚀🙏 |
As discussed in #53684, can we track this change to be backported to v22.x as well? |
Once this lands, There's no LTS watch label for v22.x yet. |
This will be released in v22 first, then backported to v20.x after at least two weeks. |
It may be the most appropriate module, but why We don't expose |
What would you recommend exposing it under (if it were to be exposed at all), |
Just like other new globals I would not backport it. Anyway, that is my personal opinion, not a blocker. |
Co-authored-by: Aviv Keller <38299977+RedYetiDev@users.noreply.github.com>
Co-authored-by: Aviv Keller <38299977+RedYetiDev@users.noreply.github.com>
Co-authored-by: Aviv Keller <38299977+RedYetiDev@users.noreply.github.com>
Co-authored-by: Aviv Keller <38299977+RedYetiDev@users.noreply.github.com>
Failed to start CI⚠ Something was pushed to the Pull Request branch since the last approving review. ✘ Refusing to run CI on potentially unsafe PRhttps://github.com/nodejs/node/actions/runs/9838611309 |
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.
lgtm
lgtm |
Landed in a1869fa |
Congrats @anfibiacreativa on your 1st contribution to node core! Thank you all for taking the time to review these changes. |
This PR exposes Websocket in node:http as requested in #53684
Once we discuss, if it satisfies the requirement, we can backport to Node.js 20 and 22
CC: @mcollina @nodejs/http @manekinekko