refactor(socket): load Socket.IO client via ESM - #4224
Merged
Conversation
khassel
approved these changes
Aug 3, 2026
khassel
pushed a commit
that referenced
this pull request
Aug 4, 2026
This is a follow-up to #4224. The original PR focused on loading Socket.IO as ESM while keeping existing modules compatible. While reviewing that change, I noticed that I missed that `main.js` was still reading the client through the global `io` variable. This PR cleans that up.
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 moves Socket.IO into the browser core's ESM loading model and removes the separate classic script dependency. The existing global bridge keeps third-party modules working unchanged, while the ESM migration can continue incrementally.