Skip to content

[Enhancement] Progress bar on ng new {project_name} after "Installing packages for tooling via npm." #5960

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

Closed
pumano opened this issue Apr 14, 2017 · 5 comments · Fixed by #8154
Assignees
Labels
feature Issue that requests a new feature help wanted P5 The team acknowledges the request but does not plan to address it, it remains open for discussion

Comments

@pumano
Copy link

pumano commented Apr 14, 2017

Bug Report or Feature Request (mark with an x)

- [ ] bug report -> please search issues before submitting
- [x] feature request

Versions.

@angular/cli: 1.0.0
node: 6.9.1
npm: 4.0.2
os: Windows 10 x64

Repro steps.

ng new {projectname}

The log given by the failure.

Desired functionality.

What would like to see implemented?

Please add progress bar when new project created via "ng new {project_name} " after "Installing packages for tooling via npm."

What is the usecase?

Possibility to see progress bar as it provided by NPM / Yarn itself

Mention any other details that might be useful.

@filipesilva filipesilva added help wanted P5 The team acknowledges the request but does not plan to address it, it remains open for discussion feature Issue that requests a new feature labels May 5, 2017
@filipesilva filipesilva self-assigned this May 5, 2017
@filipesilva
Copy link
Contributor

I can see this being nice especially with slower connections.

@narainsagar
Copy link
Contributor

@filipesilva I would like to give it a shot.

@filipesilva
Copy link
Contributor

@narainsagar go for it 👍

Bear in mind this might be especially hard given that different versions of npm display progress in different ways, and so does yarn. I don't even know how other package managers deal with it.

This isn't something we'd like to add if it's a massive undertaking though, so if you see it's non-trivial just let us know.

@narainsagar
Copy link
Contributor

@filipesilva Thanks. Yeah sure - will let you guys know here. Since I also don't know much about how all package managers are exactly doing this.. So will study and share my findings here. Thanks for your positive response 👍

peternewnham added a commit to peternewnham/angular-cli that referenced this issue Oct 23, 2017
peternewnham added a commit to peternewnham/angular-cli that referenced this issue Oct 25, 2017
peternewnham added a commit to peternewnham/angular-cli that referenced this issue Oct 25, 2017
peternewnham added a commit to peternewnham/angular-cli that referenced this issue Oct 27, 2017
peternewnham added a commit to peternewnham/angular-cli that referenced this issue Oct 30, 2017
dond2clouds pushed a commit to d2clouds/speedray-cli that referenced this issue Apr 23, 2018
@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 Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature Issue that requests a new feature help wanted P5 The team acknowledges the request but does not plan to address it, it remains open for discussion
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants