Error running npm install

[federicogatti]

Cloning the project and running npm install I have this error:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: ts-jest@28.0.8
npm ERR! Found: babel-jest@29.0.1
npm ERR! node_modules/babel-jest
npm ERR!   dev babel-jest@"^29.0.1" from the root project
npm ERR!   babel-jest@"^29.0.1" from jest-config@29.0.1
npm ERR!   node_modules/jest-config
npm ERR!     jest-config@"^29.0.1" from @jest/core@29.0.1
npm ERR!     node_modules/@jest/core
npm ERR!       @jest/core@"^29.0.1" from jest@29.0.1
npm ERR!       node_modules/jest
npm ERR!         dev jest@"^29.0.1" from the root project
npm ERR!       1 more (jest-cli)
npm ERR!     jest-config@"^29.0.1" from jest-cli@29.0.1
npm ERR!     node_modules/jest-cli
npm ERR!       jest-cli@"^29.0.1" from jest@29.0.1
npm ERR!       node_modules/jest
npm ERR!         dev jest@"^29.0.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional babel-jest@"^28.0.0" from ts-jest@28.0.8
npm ERR! node_modules/ts-jest
npm ERR!   dev ts-jest@"^28.0.8" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: babel-jest@28.1.3
npm ERR! node_modules/babel-jest
npm ERR!   peerOptional babel-jest@"^28.0.0" from ts-jest@28.0.8
npm ERR!   node_modules/ts-jest
npm ERR!     dev ts-jest@"^28.0.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 /Users/federicogatti/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/federicogatti/.npm/_logs/2022-10-28T09_21_59_757Z-debug-0.log

Node version v16.17.0 npm version 8.19.2

[federicogatti]

Can someone answer my question?

[thoughtpalette]

@federicogatti Very sorry for the late update, there's an issue with some of our dependency updates (tracked in our internal backlog). You can get around this error by using the --legacy-peer-deps flag when installing. e.g. npm i --legacy-peer-deps