Describe the bug
I don't know if another port is used when the default port 3000 is already in use, but the console still prints
vite v2.8.6 dev server running at:
> Local: http://localhost:3000/
> Network: use `--host` to expose
ready in 310ms.
Reproduction
https://gitlab.com/adamjagosz/vite-test
System Info
System:
OS: macOS 11.6
CPU: (8) x64 Apple M1
Memory: 76.54 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.13.0 - ~/.nvm/versions/node/v16.13.0/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 8.1.0 - ~/.nvm/versions/node/v16.13.0/bin/npm
Browsers:
Brave Browser: 99.1.36.112
Chrome: 99.0.4844.83
Firefox: 98.0.2
Safari: 14.1.2
Safari Technology Preview: 15.4
npmPackages:
@vitejs/plugin-vue: ^2.2.0 => 2.2.4
vite: ^2.8.0 => 2.8.6
Used Package Manager
npm
Logs
No response
Validations
Describe the bug
I don't know if another port is used when the default port 3000 is already in use, but the console still prints
Reproduction
https://gitlab.com/adamjagosz/vite-test
System Info
System: OS: macOS 11.6 CPU: (8) x64 Apple M1 Memory: 76.54 MB / 16.00 GB Shell: 5.8 - /bin/zsh Binaries: Node: 16.13.0 - ~/.nvm/versions/node/v16.13.0/bin/node Yarn: 1.22.10 - /usr/local/bin/yarn npm: 8.1.0 - ~/.nvm/versions/node/v16.13.0/bin/npm Browsers: Brave Browser: 99.1.36.112 Chrome: 99.0.4844.83 Firefox: 98.0.2 Safari: 14.1.2 Safari Technology Preview: 15.4 npmPackages: @vitejs/plugin-vue: ^2.2.0 => 2.2.4 vite: ^2.8.0 => 2.8.6Used Package Manager
npm
Logs
No response
Validations