Running "ng update" does nothing and never finishes

[Swellenator]

Versions

Angular CLI: 6.0.0
Node: 10.0.0
OS: win32 x64
Angular: 5.2.1
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.6.0
@angular-devkit/core         0.6.0 (cli-only)
@angular-devkit/schematics   0.6.0 (cli-only)
@angular/cli                 6.0.0
@schematics/angular          0.6.0 (cli-only)
@schematics/update           0.6.0
rxjs                         5.5.6
typescript                   2.6.2

Repro steps

• Update cli from 1.6.3 npm install @angular/cli@6.0.0
• Update node to 10 as only had 8.4 installed
• run ng update

Observed behavior

Blinking cursor. No output. I waited 5 minutes and nothing happened. Had to Ctrl + C to quit.

Desired behavior

Should execute the command or give an error message.

Mention any other details that might be useful (optional)

I can see lots of Node.js processes being created in task manager
Is there a way to run more verbose output?

[Swellenator]

Hmmm actually it did eventually finish. Just took a really long time, like 10 minutes. I'll leave this open for a little bit in case anyone wants to chime in.

[Swellenator]

Well I suppose ng update is just painfully slow. Would be good to improve the performance.

[vajnorcan]

Well, mine is still hanging after like 10mins and I wonder if it ever will. Some progress update into the command line would be handy....

[urish]

Seems like it creates tens of sub-processes which slow down the entire system (tested with cli 6.0.3 on node 8.11.1 / win10 x64)

[amellnik]

It takes upwards of 15 minutes for my projects on a very beefy workstation, but in my case it might be interacting poorly with some enterprise security software.

[ihabZhaika]

just like @urish said, on windows 10 x64 i opened for me about 10 terminals and lot of node processed that consume memory but does not consume cpu !!, and it causes the whole system to be really slow,
i take more than 20 mins and did not finish !!

[plaetzchen79]

I am facing exactly the same problem.

Why is this issue closed?
Is there any solution?

I cant get it to work.

Ended up editing the package.json manually and do npm install.
But this wont change the angular-cli.JSON

[ihabZhaika]

@plaetzchen79
I copied the project to linux machine, did the update there and moved it back to windows

[plaetzchen79]

Sadly Linux is no option for me.

But this morging i ran "ng update" again.
I dont know exactly how long (I went to the coffee machine and did something else) but after a long while the command finished without errors.

Ok- be patient and let the computer work..
Like in the 80ies ;-)

[aydun1]

I am facing the same problem.
"ng update" finishes, but takes close to 10 minutes.
During this time my computer (with Windows 10 x64) slows to a crawl.

"System" and "Antimalware Service Executable" CPU usage also increase during update.

[yanshuf0]

I've been running ng update @angular/cli for about 15 minutes so far on my 8 core skylake i7. Seems like an unreasonable period of time to have to wait imho. In general I'm leaning more towards react if I get to be the decision maker on upcoming projects because while angular is a joy to work with it has massive bloat and slow compilation and as a JS dev I like things slick, modular and compact.

err, I needed to remove the reference to @angular/cli from my package.json, then run npm i -D @angular/cli then run update. For future readers: If you get a warning saying cli versions do not match, you need to make sure both the global and local cli version are 6.x

[thekingspaghettie]

I'm trying to do this with my co-developer and currently it's still on-going update. Time check, 30 mins and still updating. cheers

[ihabZhaika]

@aydun1 @thekingspaghettie What i suggest to workaround this issue for now, it to copy the project to linux environment, do the install/update there then copy the whole folder with the node modules

[thekingspaghettie]

Yea. This will do. Anyway, I'm just trying it.

…

On Thu, Jun 28, 2018 at 3:38 PM, Ihab Zhaika ***@***.***> wrote: @aydun1 <https://github.com/aydun1> @thekingspaghettie <https://github.com/thekingspaghettie> What i suggest to workaround this issue for now, it to copy the project to linux environment, do the install/update there then copy the whole folder with the node modules — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#10622 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AiOKwGHjaPtxPBHMLGNoc6kLNx8yslk5ks5uBIfmgaJpZM4Tx-a2> .