-
Notifications
You must be signed in to change notification settings - Fork 11.9k
Open
Labels
angular/build:unit-testarea: @angular/buildfreq1: lowOnly reported by a handful of users who observe it rarelyOnly reported by a handful of users who observe it rarelyseverity3: broken
Description
Command
test
Is this a regression?
- Yes, this behavior used to work in the previous version
The previous version in which this bug was not present was
No response
Description
When running ng test --progress=false
it returns an unknown argument when running it after vitest setup.
According to the ng test docs, it should be a supported option.
Minimal Reproduction
Change angular.json
to use vitest. Ref.
Run ng test --progress=false
Exception or Error
Error: Unknown argument: progress
Your Environment
Angular CLI: 20.0.5
Node: 22.14.0
Package Manager: npm 11.2.0
OS: linux x64
Angular: 20.0.6
Package Version
------------------------------------------------------
@angular-devkit/architect 0.2000.5
@angular-devkit/core 20.0.5
@angular-devkit/schematics 20.0.5
@angular/build 20.0.5
@angular/cdk 20.0.5
@angular/cli 20.0.5
@angular/google-maps 20.0.5
@angular/material 20.0.5
@schematics/angular 20.0.5
rxjs 7.8.2
typescript 5.8.3
zone.js 0.15.1
Anything else relevant?
No response
axelcarl
Metadata
Metadata
Assignees
Labels
angular/build:unit-testarea: @angular/buildfreq1: lowOnly reported by a handful of users who observe it rarelyOnly reported by a handful of users who observe it rarelyseverity3: broken