feat(@angular/build): add isolate option to unit-test builder - #33041
Conversation
39aa7c9 to
9d357a9
Compare
There was a problem hiding this comment.
Code Review
This pull request introduces an "isolate" option to the unit test builder, enabling test isolation when using the Vitest runner. The changes span the public API, schema definitions, option normalization, and the Vitest plugin configuration, supported by new unit tests. Review feedback identifies a bug in the validation logic where the default runner is not correctly accounted for, a conflict between isolation and debug modes, and a potential issue where CLI flags might be overridden by user configuration files.
This commit adds an `isolate` option to the `@angular/build:unit-test` builder for the Vitest runner. By default, tests run in a non-isolated environment to match the behavior of Karma/Jasmine. This new option allows developers to easily opt-in to Vitest native isolation (running tests in separate threads or processes) without requiring a custom Vitest configuration file. The option is not supported by the Karma runner and will result in an error if used there.
9d357a9 to
150c3a7
Compare
|
This PR was merged into the repository. The changes were merged into the following branches:
|
|
This pull request has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This commit adds an
isolateoption to the@angular/build:unit-testbuilder for the Vitest runner. By default, tests run in a non-isolated environment to match the behavior of Karma/Jasmine. This new option allows developers to easily opt-in to Vitest native isolation (running tests in separate threads or processes) without requiring a custom Vitest configuration file. The option is not supported by the Karma runner and will result in an error if used there.