fix: resolve Node 22 websocket crash and expose local dev server (#1) - #2
Open
hackerharsh016 wants to merge 1 commit into
Open
fix: resolve Node 22 websocket crash and expose local dev server (#1)#2hackerharsh016 wants to merge 1 commit into
hackerharsh016 wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
shouldUpgradeCallback if it's missing. This prevents the Vite dev server from crashing with a TypeError when establishing a WebSocket
connection over HTTPS (a known regression in Node.js 22.21.0's http2 module).
( 0.0.0.0 ) instead of just localhost . This resolves the issue where mobile phones scanning the QR code were unable to reach the host
machine.