Extract loadConfig from YarnRegistry/NpmRegistry responsibility (reading .npmrc/.yarnrc configs)

[bestander]

Do you want to request a feature or report a bug?
code improvement

YarnRegistry extends NpmRegistry.
YarnRegistry reads .yarnrc into config object and NpmRegistry reads .npmrc into config object.

In some cases YarnRegistry is used for requests in other NpmRegistry.
This makes it confusing to track down when settings are used from .npmrc and when from .yarnrc and this causes issues like #3612

[bestander]

BTW if you want to make Yarn work better with .npmrc speak up and send a PR.

[MaxCCC]

@bestander I have defined the following .npmrc and .yarnrc:

proxy=http://prox
https-proxy=https://prox
registry=http://xxx:8081/artifactory/api/npm/npm
strict-ssl=false
maxsockets=xxx

and

registry "http://xxx:8081/artifactory/api/npm/npm"
"_auth" xxx
always-auth false
email test@mail.com
strict-ssl false
maxsockets "xxx"

I've deleted our node_modules and yarn.lock

Now when we the yarn install is executed:

[INFO] [1/4] Resolving packages...
verbose: GET request to http://xxx:8081/artifactory/api/npm/npm
[INFO] [2/4] Fetching packages... (fail)
verbose: Performing "GET" request to "https://xxx/artifactory/api/npm/npm/xxx.tgz".

Why is it resolving to https during the fetch? We want to keep everything on http. Everything is internal.
yarn config list just before the install shows only the right http url's.

[yyjazsf]

I think: when use yarn
project's .yarnrc > project's .npmrc > global .yarnrc > global .npmrc

[yyjazsf]

This is also worth considering.
yarn only use .yarnc.
npm only use .npmrc
if someone use yarn, they should use yarn's file. It's no friendly

[paul-soporan]

Closing as in v2 we've decided to only read .yarnrc.yml files.

https://yarnpkg.com/getting-started/migration