Angular-cli: 'ng' commands continue to be very slow to START executiing

Created on 8 Dec 2016 · 5Comments · Source: angular/angular-cli

Please provide us with the following information:

OS?

Mac OSX Sierra

Versions.

1.0.0-beta.19-3 (any ng 'X' command is extremely slow to START executing

Repro steps.

Type ng serve. It will take around 1 minute to START execution. Most ng 'xxx' are the same. (eg: ng --version)

The log given by the failure. : Not applicable

Mention any other details that might be useful.

I've mentioned this before in #2791 (for ng --version). Continues to be an issue for every command. Not sure if this is a bug or something quirky with my iMac. I don't experience it for any other NPM package. The was happening in previous version of cli AND Yosemite as well.
NOTE: I've un/re installed multiple times.

Source

momoadeli

👍3

Most helpful comment

Why not add a terminal mode to cli, such as "ng term" which just opens a prompt into which you can type several commands? this would "solve" the startup time issue with very little effort.

jdhenckel on 19 Apr 2018

👍8 👀1

All 5 comments

There is a LOT of requires done when you start the command. We are working on this.

Although https://github.com/angular/angular-cli/issues/3199 is tracking install time, I also reduced significantly the amount work (from 5 seconds to 3 when developing locally, where we also compile TS). I'm closing this as this is vague, but I added a point to that issue to drop bootstrap time as well.

hansl on 9 Dec 2016

@hansl , I want to be clear this is not about execution times of various commands. As indicated, this is about starting execution. Is that what you're referring to by 'bootstrap time'? Thanks!

momoadeli on 9 Dec 2016

Yes.

hansl on 9 Dec 2016

👍4

Why not add a terminal mode to cli, such as "ng term" which just opens a prompt into which you can type several commands? this would "solve" the startup time issue with very little effort.

jdhenckel on 19 Apr 2018

👍8 👀1

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._}