ng update ignores proxy config #13166

daniel-seitz · 2018-12-11T08:37:57Z

Bug Report or Feature Request (mark with an `x`)

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

Command (mark with an `x`)

- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [x] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

issue was partially discussed here (#10624) after .npmrc issues and later (original issue solved) determined that there is a different issue.

we use yarn with a private repo behind a corporate proxy.
local .npmrc:
registry=[some url, masked out] always-auth=true
yarn lock contains packages where I see some as resolved with [some url, masked out]
also there are packages with https://registry.yarnpkg.com/some-package-and-so-on
global .yarnrc (in C:\Users\MyUserName):

# THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY.
# yarn lockfile v1
lastUpdateCheck 1543945019859

global .npmrc (in C:\Users\MyUserName):

//some_path_with_some_token
proxy= http://our_proxy_with_port/
https-proxy= http://our_proxy_with_port

trying to follow commands from update.angular.io
yarn install works, everything else from 6. works but not ng update @angular/cli, message comes up after a while (1 minute or so):
request to https://registry.npmjs.org/@types%2fjasmine failed, reason: connect ETIMEDOUT
seems to be on a random package, at another try I got:
request to https://registry.npmjs.org/codelyzer failed, reason: connect ETIMEDOUT [some ip address and port]

Assumption:

It seems that ng update @angular/cli ignores the proxy since it should go to the configured proxy or https-proxy instead of npmjs.org.

Should the command be ng update @angular/cli@next? (Results in same error message)
P.S. I tried migrate only - which works - and then update the packages via yarn, also works.
I just think that I might miss something that ng update does as well, other than migrating to the angular.json file and lifting the packages to the recent version.

currently still running angular 5.1.1
tried as described with @next option in yarn global add @angular/cli@next and yarn add @angular/cli@next
ng --version:

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/


Angular CLI: 7.2.0-beta.1
Node: 8.12.0
OS: win32 x64
Angular: 5.1.1
... animations, common, compiler, compiler-cli, core, forms
... http, platform-browser, platform-browser-dynamic
... platform-server, router

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.12.0-beta.1
@angular-devkit/core         7.2.0-beta.1
@angular-devkit/schematics   7.2.0-beta.1
@angular/cli                 7.2.0-beta.1
@angular/language-service    4.4.6
@schematics/angular          7.2.0-beta.1
@schematics/update           0.12.0-beta.1
rxjs                         5.5.3
typescript                   2.4.2

The text was updated successfully, but these errors were encountered:

catull · 2018-12-11T14:05:32Z

@alan-agius4
The same .npmrc is used to initially retrieve all dependencies listed in package.json w/ npm install.

Thus, the configuration is not the problem, such as firewall rule that causes a time-out.

clydin · 2018-12-11T15:59:52Z

@daniel-seitz If you are running the latest beta can you try running update with the --verbose option and report the output?

I'll also push a PR (and hopefully get it into beta.2) that will expand the verbose output to also include the final set of options to further aid in troubleshooting.

daniel-seitz · 2018-12-13T15:14:49Z

@clydin thank for for pushing, I tested verbose with beta.2
For each dependency in package.json this is written:


Locating potential npmrc files:
Trying 'C:\Program Files\nodejs\etc\npmrc'...not found.
Trying 'C:\Users\my_user_name\.npmrc'...found.
Trying 'C:\Users\.npmrc'...not found.
Trying 'C:\Users\my_user_name\.npmrc'...found.
Trying 'C:\Users\my_user_name\source\.npmrc'...not found.
Trying 'C:\Users\my_user_name\source\repos\.npmrc'...not found.
Trying 'C:\Users\my_user_name\source\repos\NameOfRepoLocation\.npmrc'...not found.
Trying 'C:\Users\my_user_name\source\repos\NameOfRepoLocation\OurRepo\.npmrc'...found.

Locating potential yarnrc files:
Trying 'C:\Program Files\nodejs\etc\yarnrc'...not found.
Trying 'C:\Users\my_user_name\.yarnrc'...found.
Trying 'C:\Users\.yarnrc'...not found.
Trying 'C:\Users\my_user_name\.yarnrc'...found.
Trying 'C:\Users\my_user_name\source\.yarnrc'...not found.
Trying 'C:\Users\my_user_name\source\repos\.yarnrc'...not found.
Trying 'C:\Users\my_user_name\source\repos\NameOfRepoLocation\.yarnrc'...not found.
Trying 'C:\Users\my_user_name\source\repos\NameOfRepoLocation\OurRepo\.yarnrc'...not found.

So in total more than 50 times this whole block here. Could be enhanced but this is another story.
Then it takes a while until:

request to https://registry.npmjs.org/jasmine-core failed, reason: connect ETIMEDOUT

Interestingly in my yarn.lock there are 2 entries for jasmine-core:

[email protected]
   version: 2.5.2
   resolved: "our-proxy/jasmine-core/..."

jasmine-core@~2.8.0
   version: 2.8.0
   resolved: "https://registry.yarnpkg.com/jasmine-core/..."

Not sure if that is normal.
Deleted yarn.lock.
Did yarn install again,
then yarn add @angular/cli@next
and ng update @angular/cli --verbose
--> same timeout result

request to https://registry.npmjs.org/@angular%2fcompiler-cli failed, reason: connect ETIMEDOUT

would be interesting why npmjs.org is asked and what the final configuration looks like.
PS Also just tried the --registry option - which says 'unable to authenticate' this should be done by npmrc.

YonatanKra · 2018-12-19T09:26:36Z

That's still not working on my end, using angular cli 7.1.3.
Had to remove all private repo deps, run the update, and put the private ones back as a workaround.

ahasall · 2018-12-19T14:11:42Z

Try ng update --registry=<your_internal_registry>.

dmnk · 2019-01-03T07:33:31Z

dupe of #10952 ?

woppa684 · 2019-01-08T07:43:06Z

Try ng update --registry=<your_internal_registry>.

That won't work in our environment however ...

Unable to authenticate, need: Bearer, Basic realm="<our base URI>", Negotiate, NTLM

Soeren86n · 2019-01-08T08:15:54Z

Try ng update --registry=<your_internal_registry>.

same like before. request to http://registry.npmjs.org/@angular%2flanguage-service failed, reason: connect ETIMEDOUT 104.16.19.35:80

santoshyadavdev · 2019-01-10T10:09:50Z

Same error here, it is somhow trying to connect to https://registry.npmjs.org don't know why, i already have registry set to my artifactory.
request to https://registry.npmjs.org/@angular%2fplatform-browser failed, reason: connect ETIMEDOUT 104.16.16.35:443

ndraiman · 2019-01-13T12:01:30Z

Try ng update --registry=<your_internal_registry>.

@ahasall Worked for me, also behind corporate proxy with our own registry

mgechev · 2019-01-13T18:57:38Z

@nexxado, thanks for sharing :)

dmnk · 2019-01-14T06:41:23Z

@mgechev, i think you've been a bit quick on the draw. Most of us don't have the chance to use internal registries, and OF COURSE it works, if you're accessing an internal service, no matter if the proxy configuration is respected by ng updated. (which seems to be NOT the case).

mgechev · 2019-01-14T07:38:20Z

@dmnk yep, you're right. Just reopened.

woppa684 · 2019-01-14T07:53:38Z

Also relates to my comment here #9646 (comment)

CSchulz · 2019-01-17T09:54:14Z

Can you retry it with 7.2.2? It fixed our issue with the project npmrc file.

clydin · 2019-03-01T19:23:53Z

This should now be corrected with the latest version of the CLI. If anyone is still encountering problems, please open a new issue detailing the problem.

daniel-seitz · 2019-05-04T13:44:50Z

Sorry for the time off and missing feedback from my side. I'm assigned to another project and can't really test it anymore.
@clydin I saw the new documentation and corresponding changes, thank you for this! And @everybody-here thank you for your effort.

daniel-seitz · 2019-05-27T13:19:33Z

Back in the original project - just tried with @angular/[email protected]
It works. Thank you again, done.

angular-automatic-lock-bot · 2019-09-09T14:41:30Z

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

alan-agius4 added the comp: schematics/update label Dec 11, 2018

ngbot bot added this to the needsTriage milestone Dec 11, 2018

mgechev closed this as completed Jan 13, 2019

mgechev reopened this Jan 14, 2019

clydin closed this as completed Mar 1, 2019

angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 9, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ng update ignores proxy config #13166

ng update ignores proxy config #13166

daniel-seitz commented Dec 11, 2018

catull commented Dec 11, 2018

clydin commented Dec 11, 2018

daniel-seitz commented Dec 13, 2018 •

edited

Loading

YonatanKra commented Dec 19, 2018

ahasall commented Dec 19, 2018

dmnk commented Jan 3, 2019

woppa684 commented Jan 8, 2019

Soeren86n commented Jan 8, 2019

santoshyadavdev commented Jan 10, 2019 •

edited

Loading

ndraiman commented Jan 13, 2019 •

edited

Loading

mgechev commented Jan 13, 2019

dmnk commented Jan 14, 2019

mgechev commented Jan 14, 2019

woppa684 commented Jan 14, 2019

CSchulz commented Jan 17, 2019

clydin commented Mar 1, 2019

daniel-seitz commented May 4, 2019

daniel-seitz commented May 27, 2019

angular-automatic-lock-bot bot commented Sep 9, 2019

ng update ignores proxy config #13166

ng update ignores proxy config #13166

Comments

daniel-seitz commented Dec 11, 2018

Bug Report or Feature Request (mark with an x)

Command (mark with an x)

catull commented Dec 11, 2018

clydin commented Dec 11, 2018

daniel-seitz commented Dec 13, 2018 • edited Loading

YonatanKra commented Dec 19, 2018

ahasall commented Dec 19, 2018

dmnk commented Jan 3, 2019

woppa684 commented Jan 8, 2019

Soeren86n commented Jan 8, 2019

santoshyadavdev commented Jan 10, 2019 • edited Loading

ndraiman commented Jan 13, 2019 • edited Loading

mgechev commented Jan 13, 2019

dmnk commented Jan 14, 2019

mgechev commented Jan 14, 2019

woppa684 commented Jan 14, 2019

CSchulz commented Jan 17, 2019

clydin commented Mar 1, 2019

daniel-seitz commented May 4, 2019

daniel-seitz commented May 27, 2019

angular-automatic-lock-bot bot commented Sep 9, 2019

Bug Report or Feature Request (mark with an `x`)

Command (mark with an `x`)

daniel-seitz commented Dec 13, 2018 •

edited

Loading

santoshyadavdev commented Jan 10, 2019 •

edited

Loading

ndraiman commented Jan 13, 2019 •

edited

Loading