AI ERP with agents inside the systems you run
AI phone and voice agents for real calls
LLM.coPrivate, self-hosted LLM deployments
Legal AI infrastructure for firms
AI RFP discovery and response drafting
Automatic.coBusiness process automation
CyberAttack.aiThreat detection and defense
Secure AI virtual data roomsvscode
A VS Code extension that integrates Vitest test runner directly into the editor, enabling developers to run, debug, and watch tests without leaving their IDE. It provides inline test results, coverage reporting, and performance metrics for imports.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | vitest-dev/vscode |
| Owner | vitest-dev |
| Primary language | TypeScript |
| License | MIT — OSI-approved |
| Stars | 914 |
| Forks | 119 |
| Open issues | 12 |
| Latest release | v1.50.7 (2026-06-29) |
| Last updated | 2026-06-29 |
| Source | https://github.com/vitest-dev/vscode |
What vscode is
TypeScript-based VS Code extension leveraging the TestController API to provide native test exploration and execution. Supports Node.js and Deno runtimes, debugger integration via port 9229, and coverage collection through child_process or terminal shell spawning.
Get the vscode source
Clone the repository and explore it locally.
git clone https://github.com/vitest-dev/vscode.gitcd vscode# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Requires Node.js >= 18.0.0 and Vitest >= v1.4.0; verify project dependencies match before deployment.
- Debugger port (default 9229) must be available or configured; check firewall and port conflicts in CI/dev environments.
- Configuration detection via `process.env.VITEST_VSCODE` allows conditional test config; useful for environment-specific test setup.
- Shell spawning method (`child_process` vs `terminal`) affects process isolation and environment variable handling; choose based on shell setup complexity.
- File watcher glob patterns should be tuned to avoid unnecessary reruns on large codebases; default `**/*` may be broad.
When to avoid it — and what to weigh
- Using Vitest < v1.4.0 — Extension requires Vitest >= v1.4.0 and Node.js >= 18.0.0. Older projects must upgrade dependencies first.
- VS Code < 1.77.0 — Minimum VS Code version is 1.77.0; older installations cannot use this extension. Coverage features require >= 1.88.0.
- Non-JavaScript Test Frameworks — Extension is Vitest-specific. Teams using Jest, Mocha, or other frameworks will need alternative extensions or CLI tools.
- Complex Multi-Workspace Setups Without Configuration — Requires explicit configuration of workspace or root config file paths. Auto-discovery relies on glob patterns; non-standard layouts may need manual setup.
License & commercial use
MIT License (OSI-approved permissive license). Allows unrestricted commercial use, modification, and distribution with attribution.
MIT license permits commercial use without restriction. No vendor lock-in or commercial licensing required. Install from VS Code Marketplace without licensing friction.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Strong |
| Assessment confidence | High |
Debugger listens on configurable TCP port (default localhost:9229); ensure `vitest.debuggerAddress` is not exposed to untrusted networks. Execution of arbitrary test CLI arguments via `vitest.cliArguments` should be restricted in shared environments. Shell spawning method may execute environment-specific commands; review shell configuration for injection risks.
Alternatives to consider
Jest Runner (first-class extension)
If project uses Jest instead of Vitest; similar in-editor test execution and debugging features.
Test Explorer UI (generic testing extension)
Multi-framework testing UI; supports various test runners but may lack Vitest-specific optimizations like import duration display.
Vitest CLI + Custom Shell Alias
No IDE integration required; teams preferring terminal-based workflows can use `vitest --watch --reporter=verbose` with custom scripts.
Build on vscode with DEV.co software developers
Install the Vitest extension from the VS Code Marketplace to run and debug tests without leaving your editor. Configure it for your project in minutes.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
vscode FAQ
Can I use this extension with monorepos?
What should I do if the extension cannot find Vitest?
How does coverage reporting work?
Can I debug tests with custom Node arguments?
Custom software development, end to end
Standing up vscode properly takes more than a deploy. As a software development agency, DEV.co handles the open-source testing architecture, the web development on top, and the operational work underneath.
Streamline Your Testing Workflow
Install the Vitest extension from the VS Code Marketplace to run and debug tests without leaving your editor. Configure it for your project in minutes.