Bug: EAS Build Runner - NPM Registry Precedence

Expo Application Services (EAS)
1
  1. Bare workflow
  2. eas-cli: 0.48.2
  3. I’ve tested this locally and tried creating the .npmrc file with $eas_build_cache_url as the registry inside the project as a part of the pre-build hook.

According to the NPM docs, any detectable .npmrc should override the resolved filed inside of package-lock.json as of npm v7. This is not the behavior I am currently experiencing. I have tested that functionality locally and it works with both a global npmrc and one local to the project. However when I upload to the build server, the resolved field is used every time.