From a234234373d8299f857f5109cbf0ed03a887d476 Mon Sep 17 00:00:00 2001
From: Panagiotis Papadopoulos <pano_90@gmx.net>
Date: Mon, 27 Jan 2025 07:54:48 +0100
Subject: [PATCH] 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
---
 .npmrc       | 1 -
 package.json | 5 +++++
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/.npmrc b/.npmrc
index a00d1ad82..31dcbb1a6 100644
--- a/.npmrc
+++ b/.npmrc
@@ -1,2 +1 @@
 save-prefix = ''
-legacy-peer-deps = true
\ No newline at end of file
diff --git a/package.json b/package.json
index fe0fe46b7..78bf1250b 100644
--- a/package.json
+++ b/package.json
@@ -211,5 +211,10 @@
     "webpack": "5.97.1",
     "webpack-cli": "6.0.1",
     "webpack-dev-middleware": "7.4.2"
+  },
+  "overrides": {
+    "@mind-elixir/node-menu": {
+      "mind-elixir": "$mind-elixir"
+    }
   }
 }