`regression`: npmrc should be obeyed during nx migrate

Looks like it was fixed before and resurrected again: https://github.com/nrwl/nx/pull/6781

Current Behavior

Calling nx migrate 'my-package' does not obey registry settings from .npmrc. This leads to things like trying to pull latest from npm, or yarn registry instead of the registry pointed to by the workspace.

If an enterprise workspace was using a private registry, and had a custom nx plugin, they would not be able to use nx migrate for their internal migration scripts.

Expected Behavior

Registries and authorization headers in .npmrc should be obeyed by nx migrate

Steps to Reproduce

• create .npmrc
• link to the local registry nx migrate 'my-package'

Failure Logs

• nx migrate ignoring npmrc and failing when can’t fone package on npm or yarn registry.

Environment

• macos Monterey 12.4
• nx - 14.0.3
• node - 16.14.2
• yarn - 1.22.11
• npm - 8.5.0

[colinscz]

Hi @AgentEnder

1. Is there an update on when this ticket will be fixed/merged?

I am also developing inside a company network and this causes a lot of trouble because Nx is ignoring the defined proxy configurations and it’s not usable for migrations/updates. In my company certain operations outside of the defined configurations/folders in the *.npmrc are completely blocked.

1. Is there any workaround you have in mind or you can suggest to do nx migrations in the meantime untils this is fixed?

I saw there has been a release for Nx 14 but unless this is patched in Nx 13 I would have to do the whole migration manually for Angular 14 and Nx 14 which would be frustrating. Worst case we would have to abandon Nx completely as this generates more overhead then benefits as of now…

I appreciate any idea on how to work around this - unfortunately I cannot move the project outside of the company network, that would have been a way to solve it temporarily.

Thanks!

Environment

• Windows 10
• nx - 13.10.5
• node - 16.14.2
• npm - 8.5.0

[medmans]

any news about this bug ?