Clean up browser communication protocol #51226
Merged
+84
−115
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
tmat
force-pushed
the
BrowserComCleanup
branch
from
54a8dae to
9caffcd
Compare
|
@DustinCampbell ptal |
DustinCampbell
approved these changes
Oct 17, 2025
tmat
added a commit
that referenced
this pull request
Oct 17, 2025
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.
Since we now deploy middleware and Hot Reload client together we can remove support for previous versions of the protocol between these to components.
We still need to support multiple versions of WASM runtime for projects that reference older versions.
Removes "ping" message. The implementation was incorrect and is no longer needed.
See also https://devdiv.visualstudio.com/DevDiv/_git/WebTools/pullrequest/679114 and