resolvedUrls is null in plugin's configureServer

[yuan116]

Describe the bug

Hi, I am developing a plugin for my own use
and found out the resolvedUrls is still null in plugin's configureServer after server restarted, but the printrUrls working fine

Environment:
node: v21.2.0
npm: 9.5.0

this is the little hack that I use to retrieve after server listen

before server restart

after server restart

Reproduction

https://stackblitz.com/edit/vitejs-vite-5chbdo?file=custom-vite-plugin.js

Steps to reproduce

1. npm run dev
2. randomly edit the custom-vite-plugins.js, wait for server restart
3. after server restarted, resolvedUrls is null

System Info

System:
  OS: Linux 5.0 undefined
  CPU: (6) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  Memory: 0 Bytes / 0 Bytes
  Shell: 1.0 - /bin/jsh
Binaries:
  Node: 18.18.0 - /usr/local/bin/node
  Yarn: 1.22.19 - /usr/local/bin/yarn
  npm: 9.4.2 - /usr/local/bin/npm
  pnpm: 8.10.5 - /usr/local/bin/pnpm
npmPackages:
  vite: ^5.0.8 => 5.0.10

Used Package Manager

pnpm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[bolt-new-by-stackblitz]

Start a new pull request in StackBlitz Codeflow.

• vitejs-vite-5chbdo (Open reproduction)

[XiSenao]

It seems that the front and back server instances are inconsistent.

const newServer = { name: 'newServer' };
await configureServerhook(newServer);
const server = { name: 'server' };
Object.assign(server, newServer); // server !== newServer
server.resolvedUrls = {}; 

This looks like a problem.