vscode
vscode copied to clipboard
vitest-dev
VS Code extension for Vitest
**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...
**Is your feature request related to a problem? Please describe.** When you have a nested pkg structure like root/frontend/... the extension still tries to find your package.json at root/package.json instead...
As per the modification to README.md: > - `vitest.additionalDebugConfiguration`: Properties overlayed onto the run configuration to launch the vitest for debugging. For example: `{"trace": true}`
**Describe the bug** Could not start debug with pnpm project than do not has direct vite dependency, and "vitest.commandLine" could not be applied to debug. **To Reproduce** Steps to reproduce...
**Describe the bug** Maybe I didn't use the addon in the correct way? But simply put, the addon is not working at all. After installing it, I saw the testing...
**Describe the bug** When trying to debug a specific test block, the debug process just runs all tests in the file on Windows with Yarn. **To Reproduce** Steps to reproduce...
It seems it automatically reruns the test file on file save even watch mode is off **To Reproduce** just save the test file **Expected behavior** Should not rerun on save...
**Describe the bug** Test file cannot be found if the directory contains uppercase characters. Related issue: #54 but it didn't fix if the directory contains uppercase characters. For example, If...
Currently, we cannot tell which workspace a test case belongs to from the test panel easily.
Hello, when usuing `.each` the extension can not find the tests.
