feat(@angular/build): add quiet option to suppress build noise in unit tests - #33028
Conversation
947f873 to
d60d49e
Compare
…t tests The unit-test builder currently triggers a rebuild of the application on each test run in watch mode. This causes the application builder to print a full list of built files on every rebuild, which can be quite noisy and not useful during test development. This change introduces a `quiet` option to the `@angular/build:unit-test` builder. When enabled, it suppresses the build summary and stats table from the application builder. The option defaults to `true` when running locally to provide a cleaner development experience, and defaults to `false` when running in a CI environment to ensure detailed logs are available for troubleshooting.
d60d49e to
35cbf03
Compare
There was a problem hiding this comment.
Code Review
This pull request introduces a new quiet option to the Angular build and unit-test builders, allowing users to suppress build summary and stats table output. The option defaults to true in local environments and false in CI environments to maintain visibility during automated builds. The changes include updates to the public API, option normalization logic, and the addition of comprehensive unit tests to verify the behavior across different environments. I have no feedback to provide.
|
This PR was merged into the repository. The changes were merged into the following branches:
|
|
This pull request has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
The unit-test builder currently triggers a rebuild of the application on each test run in watch mode. This causes the application builder to print a full list of built files on every rebuild, which can be quite noisy and not useful during test development.
This change introduces a
quietoption to the@angular/build:unit-testbuilder. When enabled, it suppresses the build summary and stats table from the application builder. The option defaults totruewhen running locally to provide a cleaner development experience, and defaults tofalsewhen running in a CI environment to ensure detailed logs are available for troubleshooting.