fix(eio-client): prevent infinite loop with Node.js built-in WebSocket#723
Merged
darrachequesne merged 1 commit intosocketio:3.5.xfrom Nov 17, 2025
Conversation
This is a backport of socketio/socket.io@4865f2e Related: #5194
Author
|
@darrachequesne just bringing this PR to your attention, in case you missed it. |
Member
|
Thanks for the heads-up! This was released as |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a backport of socketio/socket.io@4865f2e
Related: socketio/socket.io#5194
Would be great if we could get this backport published as a patch on 3.5.x. as we are using socket.io-client@2.5.x on Node.js 22 for various reasons and are experiencing the issue listed above.