Repository navigation
Renovate ignoring npmrc setting in configuration #47344
Unanswered
verbitan
asked this question in
Request Help
Replies: 1 comment 1 reply
|
your lookup is using Artifactory correctly the log already shows its the suspicious part is in 44.167.7 post-update the write guard compares that with that fits your per-project file workaround i would keep that workaround for now and include those path values when reporting this as an artifact generation bug rather than changing the registry lookup settings this is based on the source and your logs i have not reproduced the full GitLab run |
1 reply
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?
Self-hosted Renovate CLI
Which platform you running Renovate on?
GitLab (.com or self-hosted)
Which version of Renovate are you using?
44.167.7
Please tell us more about your question or problem
Hi,
I am trying to get Renovate to manage a repo with several npm projects inside. I want to configure
npmrcin my Renovate config to go via an Artifactory instance.{ "npmrc": "registry=https://artifactory.example.com/artifactory/api/npm/npm-virtual/" }However, the
package-lock.jsonfiles submitted by Renovate change the resolved property of dependencies fromhttps://artifactory.example.com:443/artifactory/api/npm/npm-virtual/@esbuild/...tohttps://registry.npmjs.org/@esbuild/....Everything I can see from the Renovate debug logs appear to show that it has accepted and used this configuration, and should be using my alternate registry.
I created a very simple repo to test this out, the structure of which is below.
{ "name": "example1", "version": "1.0.0", "dependencies": { "esbuild": "0.26.0" }, "devDependencies": { "eslint": "10.0.0" } }{ "name": "example2", "version": "1.0.0", "dependencies": { "esbuild": "0.26.0" }, "devDependencies": { "eslint": "10.0.0" } }Curiously, if I add the files
example1/.npmrcandexample2/.npmrcwith the contentregistry=https://artifactory.example.com/artifactory/api/npm/npm-virtual/, then Renovate generates lock files as expected.This goes against the documentation at https://docs.renovatebot.com/getting-started/private-packages/#npm, which says:
Does anyone have any ideas?
Logs (if relevant)
Logs
All reactions