Use legacy-peer-deps flag in install

Use legacy-peer-deps flag in install to bypass the peer dependency
conflicts.

.github/workflows/ci.yml

@@ -57,7 +57,7 @@ jobs:
       uses: actions/setup-node@v4
       with:
         node-version: ${{ matrix.node-version }}
-    - run: npm install
+    - run: npm install --legacy-peer-deps
     - run: npm run testBuild
     - run: npm test
     - run: npm run browserTestCLI

Dockerfile

@@ -7,7 +7,7 @@ WORKDIR /servicemap-ui
 # A wildcard is used to ensure both package.json AND package-lock.json are copied
 # where available (npm@5+)
 COPY package*.json ./
-RUN npm install
+RUN npm install --legacy-peer-deps
 
 COPY . .
 RUN npm run build

README.md

@@ -42,12 +42,12 @@ Launches the application using `node dist` command and then launches TestCafe te
 
 ## How to use
 For development: 
-- Make sure npm packages are installed by running `npm install`in project root.
+- Make sure npm packages are installed by running `npm install --legacy-peer-deps`in project root.
 - Make sure you have environment variables set. `.env.example` should have all required values so you can copy it to `.env`.
 - Then you can start development server using `npm run dev`. Which watches files and updates on code changes.
 
 To run in production mode:
-- Make sure npm packages are installed by running `npm install`in project root.
+- Make sure npm packages are installed by running `npm install --legacy-peer-deps`in project root.
 - Make sure you have environment variables set. `.env.example` should have all required values so you can copy it to `.env`.
 - Build files by running `npm run build`
 - Then you can just run the app with `npm start`