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
it would be nice if you added a new hook for when vite opens the browser.
in our team we have a 'mirror-plugin' in one of our projects which mirrors the same app on another port, so that we have additional ports when using vite dev command, we use it something like this
we wanted to also open these ports (url) in browser when vite opens the browser
the problem is we open the urls on configureServer hook at server.httpServer.on('listening', ...) after checking server.config.server.open, but this does not really reflect when the browser is actually opened by vite.
it would be nice to have a hook for when vite opens the browser for a plugin like ours.
Suggested solution
add a vite plugin hook for when vite opens the browser, something like browserOpened
I don't know if there is a good way for us to expose this new hook, and this hasn't been a need other users have asked so far. You could add a middleware to check when the browser sends the first request to know that is has been opened and use that to implement this feature.
Description
it would be nice if you added a new hook for when vite opens the browser.
in our team we have a 'mirror-plugin' in one of our projects which mirrors the same app on another port, so that we have additional ports when using
vite dev
command, we use it something like thiswe wanted to also open these ports (url) in browser when vite opens the browser
the problem is we open the urls on
configureServer
hook atserver.httpServer.on('listening', ...)
after checkingserver.config.server.open
, but this does not really reflect when the browser is actually opened by vite.it would be nice to have a hook for when vite opens the browser for a plugin like ours.
Suggested solution
add a vite plugin hook for when vite opens the browser, something like
browserOpened
Alternative
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: