Deploy failed to build site

I tried deploying my site but it keeps saying deploy failed. This is my full deploy log:

7:34:25 PM: Build ready to start
7:34:27 PM: build-image version: d2c6dbeac570350a387d832f64bc980dc964ad65 (focal)
7:34:27 PM: build-image tag: v4.8.0
7:34:27 PM: buildbot version: 4aaa27647e859c2d38cfbb25901ceae1e7f3eeae
7:34:27 PM: Fetching cached dependencies
7:34:27 PM: Failed to fetch cache, continuing with build
7:34:27 PM: Starting to prepare the repo for build
7:34:27 PM: No cached dependencies found. Cloning fresh repo
7:34:27 PM: git clone https://github.com/BenHavis/CarloTheAce
7:34:32 PM: Preparing Git Reference refs/heads/main
7:34:33 PM: Parsing package.json dependencies
7:34:35 PM: Starting build script
7:34:35 PM: Installing dependencies
7:34:35 PM: Python version set to 2.7
7:34:35 PM: Downloading and installing node v16.15.1...
7:34:36 PM: Downloading https://nodejs.org/dist/v16.15.1/node-v16.15.1-linux-x64.tar.xz...
7:34:36 PM: Computing checksum with sha256sum
7:34:36 PM: Checksums matched!
7:34:39 PM: Now using node v16.15.1 (npm v8.11.0)
7:34:39 PM: Started restoring cached build plugins
7:34:39 PM: Finished restoring cached build plugins
7:34:39 PM: Attempting ruby version 2.7.2, read from environment
7:34:40 PM: Using ruby version 2.7.2
7:34:40 PM: Using PHP version 8.0
7:34:41 PM: No npm workspaces detected
7:34:41 PM: Started restoring cached node modules
7:34:41 PM: Finished restoring cached node modules
7:34:42 PM: Installing NPM modules using NPM version 8.11.0
7:34:42 PM: npm WARN config tmp This setting is no longer used.  npm stores temporary files in a special
7:34:42 PM: npm WARN config location in the cache, and they are managed by
7:34:42 PM: npm WARN config     [`cacache`](http://npm.im/cacache).
7:34:43 PM: npm WARN config tmp This setting is no longer used.  npm stores temporary files in a special
7:34:43 PM: npm WARN config location in the cache, and they are managed by
7:34:43 PM: npm WARN config     [`cacache`](http://npm.im/cacache).
7:34:44 PM: npm ERR! code ERESOLVE
7:34:44 PM: npm ERR! ERESOLVE could not resolve
7:34:44 PM: npm ERR!
7:34:44 PM: npm ERR! While resolving: react-font-awesome@1.0.3
7:34:44 PM: Creating deploy upload records
7:34:44 PM: npm ERR! Found: react@18.1.0
7:34:44 PM: npm ERR! node_modules/react
7:34:44 PM: npm ERR!   react@"^18.1.0" from the root project
7:34:44 PM: npm ERR!   peer react@"^18.0.0" from @testing-library/react@13.3.0
7:34:44 PM: npm ERR!   node_modules/@testing-library/react
7:34:44 PM: npm ERR!     @testing-library/react@"^13.2.0" from the root project
7:34:44 PM: Failed during stage 'building site': Build script returned non-zero exit code: 1 (https://ntl.fyi/exit-code-1)
7:34:44 PM: npm ERR!   5 more (react-dom, react-router, react-router-dom, ...)
7:34:44 PM: npm ERR!
7:34:44 PM: npm ERR! Could not resolve dependency:
7:34:44 PM: npm ERR! peer react@"~0.11.2" from react-font-awesome@1.0.3
7:34:44 PM: npm ERR! node_modules/react-font-awesome
7:34:44 PM: npm ERR!   react-font-awesome@"^1.0.3" from the root project
7:34:44 PM: npm ERR!
7:34:44 PM: npm ERR! Conflicting peer dependency: react@0.11.2
7:34:44 PM: npm ERR! node_modules/react
7:34:44 PM: npm ERR!   peer react@"~0.11.2" from react-font-awesome@1.0.3
7:34:44 PM: npm ERR!   node_modules/react-font-awesome
7:34:44 PM: npm ERR!     react-font-awesome@"^1.0.3" from the root project
7:34:44 PM: npm ERR!
7:34:44 PM: npm ERR! Fix the upstream dependency conflict, or retry
7:34:44 PM: npm ERR! this command with --force, or --legacy-peer-deps
7:34:44 PM: npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
7:34:44 PM: npm ERR!
7:34:44 PM: npm ERR! See /opt/buildhome/.npm/eresolve-report.txt for a full report.
7:34:44 PM: npm ERR! A complete log of this run can be found in:
7:34:44 PM: npm ERR!     /opt/buildhome/.npm/_logs/2022-06-03T23_34_43_001Z-debug-0.log
7:34:44 PM: Error during NPM install
7:34:44 PM: Build was terminated: Build script returned non-zero exit code: 1
7:34:44 PM: Failing build: Failed to build site
7:34:44 PM: Finished processing build request in 17.788255919s

hi there, give this thread a read through: