Skip to content

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

Open
cdprete wants to merge 1 commit intocodecentric:masterfrom
cdprete:chore/fix-npm-run
Open

chore: specify npm version explicitly to avoid 'npm MODULE_NOT_FOUND' error#5312
cdprete wants to merge 1 commit intocodecentric:masterfrom
cdprete:chore/fix-npm-run

Conversation

@cdprete
Copy link
Copy Markdown
Contributor

@cdprete cdprete commented Apr 27, 2026

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.

@cdprete cdprete requested a review from a team as a code owner April 27, 2026 18:33
@cdprete cdprete force-pushed the chore/fix-npm-run branch 4 times, most recently from 849d55a to 53b67f9 Compare April 27, 2026 18:35
@cdprete cdprete force-pushed the chore/fix-npm-run branch 5 times, most recently from c903c52 to 9372a6b Compare May 2, 2026 14:42
@cdprete cdprete force-pushed the chore/fix-npm-run branch from 9372a6b to b2dbb22 Compare May 2, 2026 18:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant