fix: unable to update the port data when it is already in use

[ilyaliao]

Description

This PR fixes the issue where data was not correctly updated when port 4000 was in use.

I noticed that listening to http.createServer() does not adequately detect if a port is already in use.

As seen in the screenshot, port 4000 is in use, but both npx vite and the notification still show port 4000.

I resolved this by installing portfinder to check for port occupancy and obtain a new port if necessary.

---

When port 4000 is in use.

When port 4001 is in use.

[antfu]

Could we use https://www.npmjs.com/package/get-port-please ? It would align more with our ecosystem and has zero-deps. Thank you

[ilyaliao]

I update it 😀

I noticed the portfinder will automatically select the host based on ipv4 or ipv6, but get-port-please seems not ...?

If the host is not ::1, get-port-please can not correct work (always return 4000).