Comments (7)
Does Vitest work for you without the extension?
from vscode.
Running vitest in the terminal without the extension works fine.
from vscode.
If it helps, vitest extension version v0.5.15 used to work when using vitest 1.4.0, however this version of the extension is not available anymore for download it seems and also it doesn't work with vitest latest 2.0.1
from vscode.
It doesn't really help. I don't think the problem is with OS, I will need a minimal reproduction to looks into this. Try creating a simple project - does it work on your PC out of the box?
from vscode.
The extension does work with the simple project so must be something in my repo that is causing it to crash. Weird that this didn't happen with v0.5.15. I'll look more into it on my side. Thanks for the quick response.
from vscode.
The extension does work with the simple project so must be something in my repo that is causing it to crash. Weird that this didn't happen with v0.5.15. I'll look more into it on my side. Thanks for the quick response.
Maybe you don't have the config in the root? The extension uses the config directory as cwd, - maybe that's why it can't find the package?
from vscode.
I actually found the problematic package. We are using rsbuild instead of vite for actually building the project and it looks like @rspack/binding-darwin-arm64 was somehow interfering. Updating this package to latest version seems to have fixed my issue.
from vscode.
Related Issues (20)
- No test output when debugging HOT 7
- Vitest failes to start in vscode >=1.90 when using Yarn PnP HOT 13
- Open VSX Registry (VSCodium) forcing outdated version (1.0.0-beta.X) HOT 7
- Vitest failed to start error on .d.ts files with v0.12.4
- Vitest process exited with exit code null HOT 2
- Color indicator of failing tests in Explorer and Tab Bar
- Debugger grinds to a halt with large unrelated files present HOT 1
- Debugging test regression after 0.10.7 HOT 3
- Plugin keeps iterating across port numbers HOT 1
- Errors during tests don't get reported correctly
- Vitest plugin fails to run tests in a monorepo with app-specific config HOT 3
- Crashes with "Cannot find module"
- `Run all Tests` doesn't create any ui/visual elements anymore
- Add "Turn on continous run" option to the right click menu HOT 1
- VS Code IDE with Docker. No tests have been found in this workspace yet. HOT 1
- Vitest plugin fails to run tests in a monorepo with app-specific config
- Logs should go to Output pane channel rather than dev console HOT 2
- Update snapshots
- Context buttons at wrong line when returning Promise from test HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vscode.