Skip to content
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

Missing build duration display after ng build in Angular v17.1.0 #27233

Closed
1 task done
HCenggel opened this issue Mar 7, 2024 · 3 comments · Fixed by #27235
Closed
1 task done

Missing build duration display after ng build in Angular v17.1.0 #27233

HCenggel opened this issue Mar 7, 2024 · 3 comments · Fixed by #27235

Comments

@HCenggel
Copy link

HCenggel commented Mar 7, 2024

Command

build

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

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

no

Your Environment

Angular CLI: 17.1.0
Node: 18.17.0
Package Manager: yarn 1.22.19
OS: win32 x64

Angular: 17.2.1
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1702.0
@angular-devkit/build-angular   17.1.0
@angular-devkit/core            17.1.0
@angular-devkit/schematics      17.1.0
@angular/cdk                    17.1.0
@angular/cli                    17.1.0
@schematics/angular             17.1.0
rxjs                            7.8.1
typescript                      5.3.3
zone.js                         0.14.4

Anything else relevant?

No response

@HyperLife1119
Copy link
Contributor

The build time logs seems to be overwritten by warning logs:

image

Once I eliminated all the warnings, I could see the build time logs:

image

@HCenggel
Copy link
Author

HCenggel commented Mar 7, 2024

The build time logs seems to be overwritten by warning logs:

image Once I eliminated all the warnings, I could see the build time logs: image

This is helpful for me.

@HCenggel HCenggel changed the title Missing build duration display after ng build in Angular v17.2.0 Missing build duration display after ng build in Angular v17.1.0 Mar 7, 2024
@alan-agius4 alan-agius4 self-assigned this Mar 7, 2024
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)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Apr 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants