node install fails - outdated node dependecies

[mnemocron]

Awesome project, I would love to host it myself with custom card sets. However, your public version seems offline and when I follow th installation instructions and run node install i get the following output

simon@soleure ~/w/ubat-game (master)> npm install                       npm ERR! code ERESOLVEnpm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: ubat-game@1.0.0
npm ERR! Found: react@16.14.0
npm ERR! node_modules/react
npm ERR!   peer react@"^0.13.0 || ^0.14.0 || ^15.0.0 || ^16.0.0" from mobx-react@4.4.3            
npm ERR!   node_modules/mobx-react
npm ERR!     mobx-react@"^4.1.3" from the root project
npm ERR!   peer react@">=0.14.7" from react-autosuggest@9.4.3
npm ERR!   node_modules/react-autosuggest
npm ERR!     react-autosuggest@"^9.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! react-bootstrap@"^0.30.8" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: react@18.3.1
npm ERR! node_modules/react
npm ERR!   peer react@"^18.3.1" from react-dom@18.3.1
npm ERR!   node_modules/react-dom
npm ERR!     peer react-dom@">=0.14.0" from react-bootstrap@0.30.10
npm ERR!     node_modules/react-bootstrap
npm ERR!       react-bootstrap@"^0.30.8" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /home/simon/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:

[matzebond]

2. Use =--legacy-peer-deps=: If you want to bypass the peer dependency conflict, you can run the installation command with the =--legacy-peer-deps= flag:

   #+begin_src bash
   npm install --legacy-peer-deps
   #+end_src

   This tells npm to ignore peer dependency conflicts, which was the behavior in npm version 6.

3. Use =--force=: As a last resort, you can use the =--force= option, but be cautious as this might lead to an unstable project if dependencies are not compatible:

   #+begin_src bash
   npm install --force
   #+end_src

Does any of this help?

[mnemocron]

According to my bash history I already tried that and got scared of the output:
132 vulnerabilities (4 low, 48 moderate, 36 high, 44 critical)

But running npm run build after npm install --legacy-peer-deps seems to build without errors.
I will try to test the app later. Thanks