You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
Describe the bug
Hi, I am developing a plugin for my own use
and found out the
resolvedUrls
is stillnull
in plugin'sconfigureServer
after server restarted, but theprintrUrls
working fineEnvironment:
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
npm run dev
custom-vite-plugins.js
, wait for server restartresolvedUrls
isnull
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
The text was updated successfully, but these errors were encountered: