build(npm): use specific overrides instead of legacy-peer-deps

allows us to handle these peer dependency
issues on a case by case basis, instead of
generally allowing it for all packages,
which could lead to unnoticed issues.

in this case the @mind-elixir/node-menu package
is still showing mind-elixir 2.x.x as peerDep,
which cannot be resolved, since we use v4
This commit is contained in:
Panagiotis Papadopoulos 2025-01-27 07:54:48 +01:00
parent c6730c5467
commit a234234373
2 changed files with 5 additions and 1 deletions

1
.npmrc
View File

@ -1,2 +1 @@
save-prefix = '' save-prefix = ''
legacy-peer-deps = true

View File

@ -211,5 +211,10 @@
"webpack": "5.97.1", "webpack": "5.97.1",
"webpack-cli": "6.0.1", "webpack-cli": "6.0.1",
"webpack-dev-middleware": "7.4.2" "webpack-dev-middleware": "7.4.2"
},
"overrides": {
"@mind-elixir/node-menu": {
"mind-elixir": "$mind-elixir"
}
} }
} }