Modules not installed from custom registry when using yarn

[timsnadden]

Is this a bug report?

Yes

Did you try recovering your dependencies?

N/A

Which terms did you search for in User Guide?

N/A

Environment

N/A

Steps to Reproduce

1. Set a custom yarn or npm registry (e.g. yarn config set registry http://registry.npmjs.org/). A more realistic example would be an npm proxy that is inside a corporate network where users may not be able to make requests directly to the public registry.
2. Create an app yarn create react-app app

Expected Behavior

Node modules are requested from the custom registry (in our example http://registry.npmjs.org/) and yarn.lock references the custom registry

Actual Behavior

Node modules are requested from the default registry (https://registry.yarnpkg.com/) and yarn.lock references the default registry. This can fail for users inside networks that can't access these URLs

[timsnadden]

This would be fixed by something like #5745

[Timer]

Closing in favor of that issue or Yarn v2 where the registry is stripped from the lockfile by default.