Skip to content

ng update doesn't work under the proxy #10241

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
valerka-xarkov opened this issue Apr 9, 2018 · 2 comments
Closed

ng update doesn't work under the proxy #10241

valerka-xarkov opened this issue Apr 9, 2018 · 2 comments

Comments

@valerka-xarkov
Copy link

valerka-xarkov commented Apr 9, 2018

Versions

Angular CLI: 1.7.4
Node: 8.10.0
OS: win32 x64
Angular: 5.2.9
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cli: 1.7.4
@angular-devkit/build-optimizer: 0.3.2
@angular-devkit/core: 0.3.2
@angular-devkit/schematics: 0.3.2
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 1.10.2
@schematics/angular: 0.3.2
@schematics/package-update: 0.3.2
typescript: 2.5.3
webpack: 3.11.0

Repro steps

  • Step 1
    I've invoked command from terminal ng update

Observed behavior

I've received an error
events.js:183
throw er; // Unhandled 'error' event
^

Error: getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:80
at errnoException (dns.js:50:10)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:92:26)

Desired behavior

I would expect the project be updated

Mention any other details that might be useful (optional)

I work under the proxy, and I don't have an option to work without it.

@bkhurram
Copy link

bkhurram commented Apr 10, 2018

I have a similar problem: ng update @angular/cli --migrate-only --from=1.7.4

events.js:183
throw er; // Unhandled 'error' event
^

Error: connect ECONNREFUSED 151.101.112.162:80
at Object._errnoException (util.js:1022:11)
at _exceptionWithHostPort (util.js:1044:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1198:14)

Angular CLI: 6.0.0-rc.2
Node: 8.11.1
OS: win32 x64
Angular: 6.0.0-rc.3
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cli: 6.0.0-rc.2
@angular-devkit/architect: 0.5.4
@angular-devkit/core: 0.5.4
@angular-devkit/schematics: 0.5.4
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 6.0.0-rc.3
@schematics/angular: 0.5.4
@schematics/update: 0.5.4
typescript: 2.9.0-dev.20180411
webpack: 4.5.0

hansl added a commit to hansl/devkit that referenced this issue Apr 11, 2018
To allow for people that use NPM proxies or local cache and dont have access
to the registry.npmjs.org

Fix angular/angular-cli#10241
hansl added a commit to hansl/devkit that referenced this issue Apr 11, 2018
To allow for people that use NPM proxies or local cache and dont have access
to the registry.npmjs.org

Fix angular/angular-cli#10241
filipesilva pushed a commit to angular/devkit that referenced this issue Apr 11, 2018
To allow for people that use NPM proxies or local cache and dont have access
to the registry.npmjs.org

Fix angular/angular-cli#10241
hansl added a commit that referenced this issue Jun 6, 2018
To allow for people that use NPM proxies or local cache and dont have access
to the registry.npmjs.org

Fix #10241
@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 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants