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
vp dev prints Vite's banner without the ready in N ms line that vite prints. Scripts that wait for that line to know the dev server is up therefore time out after vp migrate rewrites vite to vp dev.
Vite prints ready in only when global.__vite_start_time is set, and Vite's own bin/vite.js sets it. Nothing in Vite+ sets it, so the line never appears.
Reproduction
jaeger-ui's dev:check greps the dev server output for ready in and fails after migrate; the test branch works around it by also accepting the http://localhost: line (fork PR). The same banner without ready in appears with vite-plus v1.1.0, so this is not new in v1.2.0.
Suggested fix
Set global.__vite_start_time = performance.now() where vp dev starts, as Vite's CLI does, so the banner matches vite dev.
Activity
fix(cli): start vp dev/build/preview through Vite's bin script
fix(cli): start vp dev/build/preview through Vite's bin script
fix(cli): start vp dev/build/preview through Vite's bin script (#3056)