Forward WebSockets from Vite tunnels#30
Draft
mmkal wants to merge 1 commit into
Draft
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
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.
Summary
Makes the
captun/viteplugin forward WebSocket upgrades to the local Vite server, instead of only forwarding plain HTTP.This lets browser clients use the public tunnel URL for Vite HMR and other WebSocket endpoints served by the same dev server.
pkg.pr.new package for testing:
Note: use the commit alias above. The PR-number alias currently resolves to an older package artifact.
Changes
connectWebSockettocreateCaptunTunnelfrom the Vite plugin.http/httpstargets tows/wss.sec-websocket-*headers for the local WebSocket client to negotiate.connectedpayload.Verification
pnpm exec vitest run test/vite-plugin.test.tspnpm run typecheckpnpm exec oxfmt --check src/vite.ts test/vite-plugin.test.tspnpm run lintpnpm run build