Startup fails.

[zangzang]

Describe the bug

When you open a project using vitepress, it starts automatically, but it starts at some point and then stops.
I didn't give a stop command such as Ctrl+C, but it doesn't progress while asking if I want to stop the command.

But using npm run dev in terminal is not a problem.

Reproduction

It just happens at startup, and even if you start by clicking the bite press icon at the bottom, the same happens after about 10 seconds.

System Info

System:
    OS: Windows 10 10.0.22621
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H
    Memory: 20.43 GB / 31.73 GB
  Binaries:
    Node: 16.19.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.19.3 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22621.1413.0), Chromium (111.0.1661.44)
    Internet Explorer: 11.0.22621.1

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
• The provided reproduction is a minimal reproducible of the bug.

[Lonfar]

We encountered the same problem

[keman5]

We encountered the same problem

[sarvex]

@zangzang @keman5 can you check the full command executed for running the server?

@zangzang in your case there are two vite instances are running in terminal, you need to close one!

[danielfilho]

I was having this issue and this is what I found out:

The instance of VSCode for the terminal was different from my actual default terminal, where I had everything installed (VSCode was running cmd.exe but everything was set on WSL2 Ubuntu).

What you need to do to fix is:

• Open your VSCode Settings
• Find terminal.integrated.defaultProfile.windows
• Set it to the correct one (the same you use as your terminal on your system)

I hope it was helpful :)

[sun128764]

#39 same issue

[CrazyCatZhang]

I encountered the same issue.