Fix: Use ws library in Node.js 22+ for Better WebSocket Error Handling #1976
Conversation
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
TarikGul
reviewed
Feb 12, 2025
TarikGul
previously approved these changes
Feb 12, 2025
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Addresses #1975. Starting from Node.js 22, the built in WebSocket implementation does not provide detailed error messages (e.g.,
ECONNREFUSED,ETIMEDOUT). This can cause issues when handling disconnections and reconnections inpolkadot-js/api, as the errors are too generic to detect connection failures properly.This PR forces the use of the ws library in Node.js 22+. This temporarily fixes the issue, until the Node.js native WebSocket become mature enough to handle such errors.