Make ng update/ng new more verbose while installing packages

[natejgardner]

🚀 Feature request

Command (mark with an x)

• new
• build
• serve
• test
• e2e
• generate
• add
• update
• lint
• extract-i18n
• run
• config
• help
• version
• doc

Description

A clear and concise description of the problem or missing capability...

Currently, ng update silently installs packages. I'd like to have the option to see its progress. While perhaps in some environments, this command runs quickly enough not to warrant verbosity by default, for enterprise developers who are required to work in development environments that have virus scans slowing down installs, waiting several hours for ng update to install packages leaves developers unaware of what's going on. Thus the option to see the package install progress would be appreciated (especially just to know that something is still happening and avoid wasting hours of time).

Describe the solution you'd like

If you have a solution in mind, please describe it.

This could be solved by either setting the existing --verbose flag to provide this output or by providing another flag for displaying package install progress.

Describe alternatives you've considered

Have you considered any alternative solutions or workarounds?

Working at company with more developer-friendly IT security policies would be a good option 🙂

[natejgardner]

Linking the previous issue requesting the same thing: #18029 (comment)

[angular-robot]

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

[angular-robot]

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.