See associated pull request for more information.

See associated pull request for more information.

See associated pull request for more information.

See associated pull request for more information.

…lder

Added a warning in the `angular:vitest-configuration` plugin to alert users if
the `watch` option specified in their `vitest.config.ts` differs from the
Angular CLI builder's `--watch` option. Because the Angular CLI's build system
and file watcher drives the execution, the Vitest-specific `watch` option is
overridden and has no effect.

(cherry picked from commit ec10eb3)

Removing the default value of `false` for the `coverage` schema option in the
unit-test builder. When a default was present, it forced the coverage check in
the Vitest plugins to override any user-provided `coverage: { enabled: true }`
values set within a custom `vitest.config.ts`.

Removing the default explicitly allows the option to be `undefined`, respecting
the fallback behavior of the runner configuration.

The description was also updated to explicitly document how the Vitest runner
resolves the coverage configuration when the builder flag is omitted.

(cherry picked from commit 1a8376b)

… configuration

When a user specifies `test.exclude` inside their `vitest.config.ts`, the tests are correctly excluded during Vitest's execution phase. However, because the Angular CLI extracts test files earlier in the process using its own `exclude` builder option, those skipped tests are still unnecessarily compiled by esbuild in-memory.

This adds a warning to explicitly notify developers of this hidden build overhead and suggests using the Angular CLI `exclude` option instead to improve performance.

(cherry picked from commit a203dcf)

Previously, providing a --coverage-exclude CLI option to the builder would completely clobber any custom coverage.exclude items defined natively within vitest.config.ts.

This correctly merges both sources using an internal Set to prevent duplicate exclusions and preserves configurations so developers can combine global ignores alongside CLI-specific boundaries.

(cherry picked from commit 01bd5d0)

…ding Vitest configuration

When leveraging the Angular CLI to run tests with a specific set of `--reporters`, Vitest's underlying `mergeConfig` logic would normally array-concatenate the CLI reporters with any reporters defined natively inside `vitest.config.ts`. This led to duplicate output processors (e.g. running 'default' twice).

By explicitly wiping the original configurations when CLI overrides are present, the CLI now acts as a strict Source-of-Truth array replacer, which is the expected behavior for CI and custom targets.

(cherry picked from commit 355ebe8)

See associated pull request for more information.

…anguage redirects

(cherry picked from commit ca6f08c)

…y risks

This commit adds support for '*' in allowedHosts for SSR, allowing any host to be validated. It also adds a security warning when '*' is used to inform users of the potential risks of allowing all host headers.

(cherry picked from commit 3b99ee1)

(cherry picked from commit 4bbd1bf)

See associated pull request for more information.

See associated pull request for more information.