Skip to content

fix(@angular/build): use an empty array as default value for vitest exclude #30544

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 17, 2025

Conversation

cexbrayat
Copy link
Member

PR Checklist

Please check to confirm your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Issue Number: #30543

What is the new behavior?

Avoids the error resolved.coverage.exclude is not iterable while running ng test.

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

…xclude

Fixes angular#30543

Avoids the error `resolved.coverage.exclude is not iterable` while running `ng test`.
@alan-agius4 alan-agius4 added action: merge The PR is ready for merge by the caretaker target: minor This PR is targeted for the next minor release labels Jun 17, 2025
@alan-agius4 alan-agius4 merged commit 130c650 into angular:main Jun 17, 2025
33 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action: merge The PR is ready for merge by the caretaker area: @angular/build target: minor This PR is targeted for the next minor release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Vitest: resolved.coverage.exclude is not iterable in v20.1.0-next.1
2 participants