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
Vite will still use the default port 24678 for the web socket connection. This used to work in previous Nuxt3 version. My assumption is that the following commit introduced this bug: https://github.com/nuxt/framework/pull/3169/files
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered:
@antfu Is clientPort defined in defineNuxtConfig > vite > server > hmr respected at all? After updating to version 3.0.0-27408529.089160a the page started reloading because it cannot connect to HMR. We have a rule in reverse proxy for websocket where there is a fixed port. If it is to be dynamic, we cannot reasonably use Docker for local development !
Environment
Reproduction
Configure the Vite HMR port via nuxt.config.ts
Describe the bug
Vite will still use the default port 24678 for the web socket connection. This used to work in previous Nuxt3 version. My assumption is that the following commit introduced this bug: https://github.com/nuxt/framework/pull/3169/files
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: