Could not undertand how it works

[fairking]

Describe the bug

After installing the extension it shows me a white window and runs a new listener on port 4000. ???

I am not expecting this. Also the VSCode freezes when I open a project and it's doing some stuff I have no idea.

What I expect is having a standard vuejs project and launch.json to go to Debug tab and click "Launch Chrome" or whatever:
launch.json:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "type": "msedge",
            "request": "launch",
            "name": "Launch Edge",
            "url": "http://localhost:9001",
            "webRoot": "${workspaceFolder}/src"
        },
        {
            "type": "chrome",
            "request": "launch",
            "name": "Launch Chrome",
            "url": "http://localhost:9001",
            "webRoot": "${workspaceFolder}/src"
        }
    ]
}

I also have my own port number for every my project because sometimes I open and work with several projects at the same time:
vite.config.ts

server: {
        port: 9001,
        strictPort: true
    },

The way how this extension works is unknown for me and not straight forward. Just another overcomplicated stuff.

Sorry guys, just uninstalled the extension. Not suitable to me. Just my Feedback.

Reproduction

Reproduction

System Info

System:
    OS: Windows 11 10.0.22631
    CPU: (4) x64 Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz
    Memory: 13.62 GB / 23.92 GB
  Binaries:
    Node: 20.10.0 - C:\Program Files\nodejs\node.EXE
    npm: 9.2.0 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.1.3 - ~\AppData\Local\pnpm\pnpm.CMD
  Browsers:
    Edge: Chromium (127.0.2651.86)
    Internet Explorer: 11.0.22621.3527

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.

Contributions

• I am willing to submit a PR to fix this issue
• I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)