You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you use vs-code for editing/debuging over ssh against the VSCode server and Vite running on another host, or in WSL or in a Docker container, the the remote VSCode server will proxy the Vite port to the VSCode host, remapping the port number. As described earlier in #1989 by @FractalHQ this will reload the page/app every second or so.
While in my case Vite runs remotely on localhost:4000 it runs locally on localhost:. The client tries to contact the original ws://localhost:4000, which clearly doesn't work.
Would it be possible to make it use the remapped port number from the url for the ws call-back?
Reproduction
Connect from one host to another using the ssh explorer and run vite in development mode.
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
Describe the bug
When you use vs-code for editing/debuging over ssh against the VSCode server and Vite running on another host, or in WSL or in a Docker container, the the remote VSCode server will proxy the Vite port to the VSCode host, remapping the port number. As described earlier in #1989 by @FractalHQ this will reload the page/app every second or so.
While in my case Vite runs remotely on localhost:4000 it runs locally on localhost:. The client tries to contact the original ws://localhost:4000, which clearly doesn't work.
Would it be possible to make it use the remapped port number from the url for the ws call-back?
Reproduction
Connect from one host to another using the ssh explorer and run vite in development mode.
System Info
Used Package Manager
pnpm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: