Add support for Vitest VSCode Plugin and similar

[yjaaidi]

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

[angular-robot]

This feature request is now candidate for our backlog! In the next phase, the community has 60 days to upvote. If the request receives more than 20 upvotes, we'll move it to our consideration list.

You can find more details about the feature request process in our documentation.

[the-ult]

This is indeed a must, for proper DX

[jannes-bantje]

Interesting data point about this

In the experimental vitest runner of Angular v20 this worked a bit. In IntelliJ you could run a test via the button in the gutter of the test file and it would run all test of that test file. However:

• the links in the console output would lead to the bundled .js files instead of the original ones
• debugging immediately runs into an error about unrecognized parameters for ng test

[replete]

I spent a lot of time trying to make this work with the Vitest VSCode vitest.explorer extension, as mentioned earlier trying to get the AnalogJS plugin working, which adds undesired complexity ... if you can get it to work, which I could not.

Please consider improving this soon 🙏

Update: Have a hack/workaround working for now