feat: add websocket support to custom transport #461
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
83838f5 to
0d9d974
Compare
|
@plusminushalf I rebased master and |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Enables more efficient communication with RPC endpoints that support WebSockets, we have seen a reduction in latency with this change testing the bundler.
infers type from RPC URL (websocket or http)
backward compatible with http
uses consistent error parsing handling across http and ws
tested against anvil and remote rpc servers
Other notes:
Considered using NodeJs's native websocket but this requires changing the minimum supported node version to 22.4.0 (from >18.0.0 currently)