feat: resolved config port

[HomyeeKing]

Description

can't access port from resolvedConfig

Additional context

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

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.

[Shinigami92]

Could you explain more why you need this?

[HomyeeKing]

@Shinigami92 check this issue #5543

[HomyeeKing]

this pr won't fix the issue #5543 thoroughly, only works for the NO port conflict case
in port conflict case, the problem still exists, we can't get the exact listening port directly

[patak-dev]

This should be working as expected, but you need to wait until the listening event to access the port info. Check out

vite/packages/vite/src/node/server/index.ts

Line 481 in 09e2a5f

serverConfig.port = (httpServer.address() as AddressInfo).port

[HomyeeKing]

@patak-js the listening event is triggered later than the configResolved and configureServer hooks invoked, so user can't access the exact port directly unless they listen listening event by hand

[sapphi-red]

The actual port is not determined until listening event has triggered.
Also configResolved and configureServer hooks triggers before server starts (because it is needed to configure server before server starts).
So it is impossible to know the actual port in those hooks.