Angular-cli: ng update @angular/cli => Error: connect ETIMEDOUT 151.101.12.162:80

[squadwuschel]

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

Versions

Angular CLI: 6.0.3
Node: 8.9.4
OS: win32 x64
Angular: 5.0.1

Package Version

angular-devkit/architect 0.6.3
angular-devkit/core 0.6.3
angular-devkit/schematics 0.6.3
schematics/angular 0.6.3
schematics/update 0.6.3
rxjs 6.1.0
typescript 2.7.2

Repro steps

I'am behinde a proxy and the proxy settings in npm are fine so far, never got any problems until today.

I've local "old" angular cli installation 1.7.4 and I try to update this to 6.0.1

I've upgraded the global cli version to 6.0.1 works fine.

then I switch to the dir of my angular project with the package.json inside and try to

ng update @angular/cli

and then the following Error shows up:

I've found this pull which should be included, but I am not able to update
https://github.com/angular/devkit/pull/692

Desired functionality

easy upgrade to 6.x

[Sioxas]

Is there any temporary workaround?

[squadwuschel]

Is this not fixed, I can't really update to the new version until this is fixed. :-/

[DsAekb]

@squadwuschel You can update local angular-cli manually and then run the update.

npm uninstall angular-cli
npm install @angular/cli@latest
ng update @angular/cli

[squadwuschel]

@DsAekb my problem is that I've about 40 projects to update and I was hoping that I don't need to do any manual upgrade steps in the configs and so on and so I've to create a large upgrade guide for every developer who need to update his app in my company

[DsAekb]

@squadwuschel

Is this not fixed, I can't really update to the new version until this is fixed. :-/

It is fixed in newer versions, to use this fix you need to update it manually, I don't see any other way here.

[mkolisnyk-clgx]

ng update @angular/core --registry=http://registry.npmjs.org
It works for me.

[DsAekb]

@mkolisnyk-clgx angular-cli 1.7.4 doesn't support the registry option.

[dmnk]

same setup here:
non-transparent proxy, everything defined in npm's config.
ng update fails (for 7.1.4, 7.1.0 works)

I'd say thats a regression of an already fixed bug?