Add support for Vitest VSCode Plugin and similar

Open
#31,734 7 comments 118 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
angular, typescript, vscode
Domain
testing, tooling

Research direction

Start with the test command and investigate how Angular currently exposes Vitest configuration to external tools. Reproduce the limitation with the Vitest VSCode Plugin, then compare the behavior with the Analog plugin mentioned in the issue. Done means the plugin and similar integrations can discover the Angular project's Vitest configuration without switching plugins.

Written by the indexing model from the issue text.

Description

angular/build:unit-test area: @angular/build feature feature: under consideration
Command

test

Description

As Angular does not provide a Vitest plugin, it can't expose a vitest.config.ts file to 3rd party tools such as IDEs.

This means that as of today, it is impossible to use Vitest VSCode Plugin, nor WallabyJS, nor WebStorm integration etc... unless users switch to Analog plugin https://analogjs.org/docs/features/testing/vitest

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Dominant language
TypeScript
Stars
27k
Forks
11.8k
Avg merge
16h 35m
Merged PRs (30d)
176

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from angular/angular-cli

All issues in angular/angular-cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.