fix(@angular/cli): normalize yarnrc/npmrc options

[alan-agius4]

Closes #17314 and closes #16615

[kyliau]

merged label removed since PR hasn't got LGTM

[alan-agius4]

Superseded by #17358

[devoto13]

@alan-agius4 Is there a particular reason why this was closed?

Judging from this file conversion is hard-coded in NPM CLI and moving forward there is no better way than repeating it for relevant options in Angular CLI.

[alan-agius4]

@devoto13, the reason why this has been closed is because we rolled back Pacote to version 9, which is used in npm version 6 and this PR was no longer relevant. Pacote 10+ is a complete rewrite for npm 7.0

Unfortunately, the file mentioned is for npm, but in the case of the CLI we need to support other package managers.

[devoto13]

@alan-agius4 Thanks for the explanation. I saw the rollback to version 9, but thought it was more of a quick fix.

Unfortunately, the file mentioned is for npm, but in the case of the CLI we need to support other package managers.

This was actually my point. Given that code in the linked file is not something Angular CLI can re-use and that other package managers should be supported, is there any reason to delay an upgrade to newer Pacote versions? I mean NPM@7 release will not make this process any easier. The logic to normalise property names needs to be re-implemented in Angular CLI as was started by this PR.

My main reasoning for the update is that older pacote pulls plenty of older dependencies/polyfills and updating will allow to shrink some MBs from the CLI installation size.

[devoto13]

Actually never mind. Just looked through the new dependency tree and it managed to grow 2 times in size despite removing obsolete dependencies.

[angular-automatic-lock-bot]

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