-
Notifications
You must be signed in to change notification settings - Fork 12k
Missing build duration display after ng build in Angular v17.1.0 #27233
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
Labels
angular/build:application
area: @angular-devkit/build-angular
freq1: low
Only reported by a handful of users who observe it rarely
severity5: regression
type: bug/fix
Comments
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Mar 7, 2024
…gs in the presence of warnings or errors Previously, a race condition could occur due to the spinner, resulting in the deletion of the last printed log when warnings or errors were present. With this update, we ensure that logs are printed after the spinner has stopped. Fixes angular#27233
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Mar 7, 2024
…gs in the presence of warnings or errors Previously, a race condition could occur due to the spinner, resulting in the deletion of the last printed log when warnings or errors were present. With this update, we ensure that logs are printed after the spinner has stopped. Fixes angular#27233
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Mar 8, 2024
…gs in the presence of warnings or errors Previously, a race condition could occur due to the spinner, resulting in the deletion of the last printed log when warnings or errors were present. With this update, we ensure that logs are printed after the spinner has stopped. Fixes angular#27233
alan-agius4
added a commit
that referenced
this issue
Mar 8, 2024
…gs in the presence of warnings or errors Previously, a race condition could occur due to the spinner, resulting in the deletion of the last printed log when warnings or errors were present. With this update, we ensure that logs are printed after the spinner has stopped. Fixes #27233
alan-agius4
added a commit
that referenced
this issue
Mar 8, 2024
…gs in the presence of warnings or errors Previously, a race condition could occur due to the spinner, resulting in the deletion of the last printed log when warnings or errors were present. With this update, we ensure that logs are printed after the spinner has stopped. Fixes #27233 (cherry picked from commit 518afd8)
alan-agius4
added a commit
that referenced
this issue
Mar 8, 2024
…gs in the presence of warnings or errors Previously, a race condition could occur due to the spinner, resulting in the deletion of the last printed log when warnings or errors were present. With this update, we ensure that logs are printed after the spinner has stopped. Fixes #27233 (cherry picked from commit 518afd8)
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
angular/build:application
area: @angular-devkit/build-angular
freq1: low
Only reported by a handful of users who observe it rarely
severity5: regression
type: bug/fix
Command
build
Is this a regression?
The previous version in which this bug was not present was
17.0.0
Description
In Angular version 17.0.0, the ng build command used to display the duration of the build process in the console after the packaging was completed. However, starting from version 17.1.0, this helpful feature seems to be missing. As a result, developers are no longer provided with the build duration information, making it difficult to assess the performance and optimization of the build process. It is important to address this bug and restore the display of build duration in the console after executing ng build.
Minimal Reproduction
no
Exception or Error
Your Environment
Anything else relevant?
No response
The text was updated successfully, but these errors were encountered: