`unit-test` builder should show a warning if vitest version is known to be incompatible

[yjaaidi]

Command

test

Description

It would be nice to add a version range for Vitest and friend packages (e.g. @vitest/browser-*) to make sure users are not using known incompatible versions.

For instance, some isolation issues were fixed in 4.0.6 and 4.0.7.

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

[alan-agius4]

Vitest already warns when vitest and @vitest/* have mismatched patch versions, so I don't believe we need to add another warning. In addition the peer dependency has already been configuring 4.0.6 as the current minimum supported version.

We could potentially update the peer dependency version range again later before the final release.

[yjaaidi]

You're right, the CLI could only check the vitest package.
Peer deps are sadly often ignored but it's probably enough. That's why there such a check for typescript version right? Vitest could deserve the same treatment.

Also, I think the minimum should be 4.0.7 as it propagates isolate option to the browser the way Angular CLI is expecting it.
Right now, 4.0.6 will have isolation on by default in browser mode.

[alan-agius4]

Will actually update it to 4.0.8, once we are able to consume it.