Is it possible to tie packageManager updates to nvm?
#40421
Unanswered
benedfit
asked this question in
Request Help
Replies: 0 comments
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?
42.74.5
Please tell us more about your question or problem
I currently have a number of repositories that use
.nvmrcfor managing node versions. In the past I have relied on the default version ofnpmthat is installed via the nvm image. Recently I have a number of project that are using thepackageManagerfield inpackage.jsonand Renovate has started offering upgrades to the version ofnpm. However, this now means that when folks runnvm install|use, they are likely on an older version ofnpmthan the one Renovate is using, resulting in thrashing of thepackage-lock.jsonfile.So I'm interested to know if there is a recommended way to link the two tools? Either by limiting the upgrade of
npmversions to only supported by the images, or forcingnvmto install/use a particular version ofnpm?Thanks in advance for any help
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions