npm install --legacy-peer-deps
--force: will force npm to fetch remote resources even if a local
copy exists on disk.
--legacy-peer-deps: ignore all peerDependencies when installing, in the style
of npm version 4 through version 6.
--strict-peer-deps: fail and abort the install process for any conflicting
peerDependencies when encountered. By default, npm will
only crash for peerDependencies conflicts caused by the
direct dependencies of the root project.
--legacy-peer-deps: ignore all peerDependencies when installing,
in the style of npm version 4 through version 6.
--strict-peer-deps: fail and abort the install process for any conflicting peerDependencies
when encountered. By default, npm will only crash for peerDependencies conflicts caused by
the direct dependencies of the root project.
try --force before --legacy-peer-deps
npm install --legacy-peer-deps
check here: https://stackoverflow.com/questions/66239691/what-does-npm-install-legacy-peer-deps-do-exactly-when-is-it-recommended-wh