If HMR is disabled, I think it's not necessary to connect to websocket

[hipi]

Clear and concise description of the problem

when

server:{
  hmr:false,
}

packages/vite/src/client/client.ts should not connect to Websocket

Suggested solution

packages/vite/src/client/client.ts add configuration

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[clement4saunier]

This is so evident and takes so much time to be treated it's disappointing, I love vite but if my production site refreshes the page every minute because of a websocket it don't need, I can't disable it for some reasons and nothing gets done about it for months why bother.

[ctburenski]

This was unexpected behaviour for me - I had this occur when using codespaces, and the page continued to refresh when it was disabled.

I tried opening the port for HMR, but the port-forwarding on codespaces maps ports to subdomains, and I decided to develop locally instead of trying to find a way to tell Vite to use a completely different url or set up a reverse proxy just for HMR.

[bluwy]

The websocket is used for more than just HMR, including showing error overlay from server and trigger full page reloads from plugins. Having server.hmr: false turn those off could be confusing (maybe not as destructive if we have docs). Otherwise perhaps #6090 might help here too.

[sapphi-red]

This feature request seems to be requested to prevent the infinite reload problem.
I'm closing this issue because #9007 fixed that problem.
If there is other reasons, please create a new issue with the reason.