-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable embedded browser. #22
Comments
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When I open Vite project in VS code it opens an embedded browser. That browser doesn't work well for me. I'd like to disable that, but the documented options don't seem to work.
My first attempt was based on the instructions found at https://vitejs.dev/config/#server-https . It says that I can specify a boolean for server.open in the config file. I set that value to false in my vite.config.ts. VS Code validated that I had the right syntax. You can see the entire config file in the Reproduction section, below.
Further googling brought me to this page. vitejs/vite#2552. That suggests that there might be a workaround using command line arguments. I'm willing to try, but I don't know where the command line is! I have installed the Vite plugin for VS code and I have created a config file. That combination is all it takes to bring up that embedded browser each time I restart VS code or reopen this project.
I appreciate any help you can offer.
Reproduction
https://github.com/TradeIdeasPhilip/bounce-3d/blob/master/vite.config.ts
System Info
npx envinfo --system --npmPackages '{vite,@vitejs/*}' --binaries --browsers
System:
OS: macOS 12.3.1
CPU: (8) arm64 Apple M1
Memory: 239.16 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 18.0.0 - ~/.nvm/versions/node/v18.0.0/bin/node
npm: 8.6.0 - ~/.nvm/versions/node/v18.0.0/bin/npm
Browsers:
Chrome: 101.0.4951.64
Safari: 15.4
npmPackages:
vite: ^2.9.9 => 2.9.9
Originally reported here vitejs/vite#8332 but they sent me to you,
The text was updated successfully, but these errors were encountered: