Renovate still try to use NPM v7, despite i'm using the configuration "force.constraints.node" #9104
-
I've read the documentation in order to use the "old" NPM v6 (the constraints setting). My current
{
"extends": [
"config:base",
":disablePeerDependencies"
],
"packageRules": [
{
"depTypeList": [
"devDependencies"
],
"rangeStrategy": "bump"
}
],
"force": {
"constraints": {
"node": "< 15.0.0"
}
}
} I've received two new PRs and they still want to use the new NPM version (look at the diffs in What I'm doing wrong, why it's not working as documented? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
Remove your force statement (recommended), or add an npm constraint to it. Right now your forced constraints are overriding the detected npm constraint, so in the absence of any npm constraint the latest npm is being installed. |
Beta Was this translation helpful? Give feedback.
-
This is not a bug, because you override the detected constraints, renovate has no npm version, so it will install latest npm (as pointed by npmjs). So best is to not use force override. Alternatively you need to add a npm constraint too. |
Beta Was this translation helpful? Give feedback.
This is not a bug, because you override the detected constraints, renovate has no npm version, so it will install latest npm (as pointed by npmjs).
So best is to not use force override. Alternatively you need to add a npm constraint too.