Libing Chen

@simonmarshall I will take a look. Now I use `RunAnything` to launch Vitest tests instead of `Run Configuration`. Maybe I should choose Run Configuration to launch Vitests, and then you...

@donalmurtagh @simonmarshall Debug support implemented with version 0.6.0 

> next request: please support _coverage_ as well as _debug_! :) Please add `c8` dependency in package.json and reopen the project. If c8 found in package.json, and Vitest Runner will...

> awesome @linux-china - thanks! it assumes our working directory is the project root, so we have to manually adjust each run config to add the appropriate sub-folder, but i...

@simonmarshall c8 should be declared in root package.json. Vitest runner will not detect every package.json in sub projects. ```json { "devDependencies": { "c8": "^7.12.0" } } ```

Could you try `"@vitest/coverage-c8": "^0.22.1",` for a test? 

@krivachy Now Vitest Runner plugin does not use Run/Debug configurations to run test, and it uses CLI+Console to run Vitest. A solution is to tell the plugin choose Vitest config...

@baiwusanyu-c it works well in terminal? Could you upgrade to WebStorm 2022.3 for a trial? It's caused by color output, and I have no idea about your WebStorm configuration. Could...

A weird question here, and vitest-jetbrains-plugin uses npx to run test. Could you upgrade the plugin to last version? You can do another test by `Run Anything`. Press Alt +...

Maybe a bug caused by `.cmd` ext name. Could you try attached version? [vitest-jetbrains-plugin-0.5.0.zip](https://github.com/linux-china/vitest-jetbrains-plugin/files/9223026/vitest-jetbrains-plugin-0.5.0.zip)