Repository navigation
Renovate ignoring npmrc setting in configuration #47360
Unanswered
verbitan
asked this question in
Request Help
Replies: 1 comment 2 replies
|
Copy the root cp .npmrc example1/.npmrc
cp .npmrc example2/.npmrcThe metadata lookup is using your mirror. The problem is the lockfile step: Renovate 44.180.0 finds the root |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
How are you running Renovate?
A Mend.io-hosted app
Which platform you running Renovate on?
GitHub.com
Which version of Renovate are you using?
44.180.0
Please tell us more about your question or problem
Current behavior
Renovate is not respecting the
npmrcconfiguration for the registry whenresolving dependencies, leading to incorrect package resolutions.
Expected behavior
Renovate should ignore the
.npmrcfile in the repository and use theconfiguration provided in the Renovate configuration property
npmrcinstead.https://docs.renovatebot.com/getting-started/private-packages/#npm
Minimal reproduction
In https://github.com/verbitan/renovate_issue_npmrc I have:
.npmrcfile in the root of the repo which overrides the registry withregistry=https://registry.npmmirror.com/..renovate.jsonwhich also setsregistry=https://registry.npmmirror.com/.The merge requests created by Renovate have ignored the
npmrcsetting and updated thepackage-lock.jsonfiles withhttps://registry.npmjs.orgrather thanhttps://registry.npmmirror.com.Logs (if relevant)
Logs
All reactions