Skip to content

Conversation

clydin
Copy link
Member

@clydin clydin commented Oct 13, 2025

This commit updates the version of vitest and its related packages from 3.2.4 to 4.0.0-beta.17 within the unit testing system.

This major version update for Vitest introduces several changes that are addressed here:

  • The coverage.all option has been removed in Vitest v4. Accordingly, the coverageAll option has been removed from the unit-test builders schema and its usage has been removed from the Karma and Vitest test runner implementations.
  • The browser provider mechanism has been updated. Vitest now uses provider-specific packages (e.g., @vitest/browser-playwright) instead of the general @vitest/browser package. The browser configuration setup has been made asynchronous and now dynamically loads the appropriate provider.
  • A workaround has been added to filter non-string values from the resolved coverage exclude patterns. This prevents an error caused by Vitest incorrectly adding boolean values into the array.

@clydin clydin added the target: major This PR is targeted for the next major release label Oct 13, 2025
@angular-robot angular-robot bot added area: build & ci Related the build and CI infrastructure of the project area: @angular/build labels Oct 13, 2025
@clydin clydin force-pushed the unit-test/update-vitest-v4-beta branch from 8503c47 to c298eee Compare October 13, 2025 19:06
This commit updates the version of `vitest` and its related packages from `3.2.4` to `4.0.0-beta.17` within the unit testing system.

This major version update for Vitest introduces several changes that are addressed here:
- The `coverage.all` option has been removed in Vitest v4. Accordingly, the `coverageAll` option has been removed from the unit-test builders schema and its usage has been removed from the Karma and Vitest test runner implementations.
- The browser provider mechanism has been updated. Vitest now uses provider-specific packages (e.g., @vitest/browser-playwright) instead of the general @vitest/browser package. The browser configuration setup has been made asynchronous and now dynamically loads the appropriate provider.
- A workaround has been added to filter non-string values from the resolved coverage exclude patterns. This prevents an error caused by Vitest incorrectly adding boolean values into the array.
@clydin clydin force-pushed the unit-test/update-vitest-v4-beta branch from c298eee to 127adee Compare October 13, 2025 23:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: @angular/build area: build & ci Related the build and CI infrastructure of the project state: blocked on upstream target: major This PR is targeted for the next major release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant