fix: Honor the host param when creating a websocket server

[casret]

Description

This is similar to the 3c53f82 that fixed #2032 but for the websocket server.

---

What is the purpose of this pull request?

• [ x ] Bug fix

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[patak-dev]

LGTM. I don't know if a test case could be added, but would it be possible to get a reproduction failing for this case?

[casret]

While my actual situation involves node binding to the wrong ipv4/ipv6 stack, I would expect this commit casret@8edbb1e to raise an error since we can't bind to '8.8.8.8', but it runs fine.

On my branch it will raise:

Error: listen EADDRNOTAVAIL: address not available 8.8.8.8:24678
    at Server.setupListenHandle [as _listen2] (net.js:1301:21)
    at listenInCluster (net.js:1366:12)
    at doListen (net.js:1503:7)
    at processTicksAndRejections (internal/process/task_queues.js:81:21)

[casret]

@patak-js Anything I can do to get this merged?

[casret]

@patak-dev ping?

[patak-dev]

Sorry for the delay, lets get this one in Vite 2.8

[casret]

@patak-dev Noticed that it didn't make it in to 2.8? Is there something else I need to patch up?

[patak-dev]

Sorry @casret, we should have added it to the 2.8 milestone. Thanks @Niputi for adding it to the 2.9 milestone so we don't miss it again. There are already several PRs queued and we just released 2.8 today so I think we may start the next beta quite soon.