fix(@angular/build): improve default coverage reporter handling for vitest #30522
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…itest When using the experimental `unit-test` builder with the `vitest` runner, the default handling for the coverage reporter option has been improved to avoid a potential upstream failure within Vitest. Vitest can crash if an explicit `undefined` value is present for the `coverage.reporter` option.
clydin
added
target: minor
alan-agius4
approved these changes
Jun 11, 2025
alan-agius4
added
action: merge
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using the experimental
unit-testbuilder with thevitestrunner, the default handling for the coverage reporter option has been improved to avoid a potential upstream failure within Vitest. Vitest can crash if an explicitundefinedvalue is present for thecoverage.reporteroption.