chore: specify npm version explicitly to avoid 'npm MODULE_NOT_FOUND' error

[cdprete]

See eirslett/frontend-maven-plugin#1178

@SteKoe can't renovate be configured to keep in sync those node.version (and now npm.version) properties every time it updates the engines section under the package.json?

The Node version specified in the pom.xml was way older than the one specified under engines in the package.json.

[SteKoe]

I have pushed a renovate.json file that tries to address this issue. I also updated versions in other places, as well.

[cdprete]

I have pushed a renovate.json file that tries to address this issue. I also updated versions in other places, as well.

Good to hear.
Otherwise I was thinking about loading the package.json file in Maven and extract them on demand.

Will it track the npm version as well?

[SteKoe]

Will it track the npm version as well?

npm versions are handled independently by renovate but are now bundled in one PR, when node.js version increases. According to the docs, at least.

[cdprete]

Will it track the npm version as well?

npm versions are handled independently by renovate but are now bundled in one PR, when node.js version increases. According to the docs, at least.

Thanks.
Now I think that all the build issues on Windows are solved.
It's only missing #5303, but that's more a setup issue.