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
When starting the Vite dev server with vite, we get:
VITE v3.0.0-beta.5 ready in 322 ms
➜ Local: http://127.0.0.1:5173/
➜ Network: use --host to expose
Metaframeworks that uses createServer can opt to not print Vite's default message by not calling server.printUrls. However, this means that the metaframeworks have to resolve the URLs themselves, potentially different from Vite's actual URLs.
Expose some sort of vanity api for metaframeworks, so they can print their own message during server restart ootb, and custom logging message etc. Might be a bit far-fetched for now.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Update: Implemented in #8986
Proposal
Expose the resolved server URLs from the Vite dev and preview server, e.g.
Background
When starting the Vite dev server with
vite
, we get:VITE v3.0.0-beta.5 ready in 322 ms ➜ Local: http://127.0.0.1:5173/ ➜ Network: use --host to expose
Metaframeworks that uses
createServer
can opt to not print Vite's default message by not callingserver.printUrls
. However, this means that the metaframeworks have to resolve the URLs themselves, potentially different from Vite's actual URLs.This issue can be seen in SvelteKit, Astro, vite-plugin-qrcode
Alternative
Expose some sort of vanity api for metaframeworks, so they can print their own message during server restart ootb, and custom logging message etc. Might be a bit far-fetched for now.
Beta Was this translation helpful? Give feedback.
All reactions