[not support vitest@v0.18.0] test successfully, but loading infinitely.

Describe the bug A clear and concise description of what the bug is. I installed vitest V0.18.0,and it doesn`t work.

To Reproduce Steps to reproduce the behavior on the example project:

1. npx degit SoonIter/sooniter-lib-template-monorepo my-lib-name
2. run ni
3. go to the “test” folder
4. run this one is Ok, but the extension works fail

Expected behavior work well

Screenshots

Maybe the problem is to run-once or run-watch. Version 0.2.20

[beorn]

The latest vitest extension release, v0.2.20 (from 15 days ago), doesn’t work with vitest v0.18.1 for me. Just get an infinite spinner.

Try the example project linked to above with this:

  "devDependencies": {
    "envinfo": "^7.8.1",
    "vite": "^3.0.0",
    "vitest": "^0.18.1"
  }

[c00]

Update: The cause of the problem is that vitest tends to bind the API on ::1 (ipv6) while the plugin tries to connect on 127.0.0.1 (ipv4).

I guess vitest and the plugin both resolve localhost in a different way. That’s weird and unfortunate.

We can force vitest to listen on the ipv4 address by passing --api.host 127.0.0.1 to it, and that does make everything work. Unfortunately we can’t currently put that in the vitest.commandLine, as the plugin sets --api [port] which overwrites that.

However, if we would change the plugin code to use --api.port [port] instead, then we would be able to do this. I will create a PR to do this.

I don’t see any possible issues this could cause. All it does is create the option for people with this issue to add the host to the command line, working around the problem.

The true solution would be to resolve localhost in the same way as vitest or forcing vitest to bind on whatever the plugin resolves to. However, this is a bit out of my comfort zone. It’s probably better to come up with a solution that works (tho isn’t perfect) than to ask an open-source maintainer to do work for me.