rajeshmn47 / dream-11-clone Goto Github PK

Are you willing to add the same functionality to the other 3 sports
or
technically the project is complete

{ Currently, I'm developing a similar project in Mongo without any external APIs }

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR! react@"^18.1.0" from the root project
npm ERR! peer react@">=16.8.0" from @emotion/[email protected]
npm ERR! node_modules/@emotion/react
npm ERR! @emotion/react@"^11.9.0" from the root project
npm ERR! peer @emotion/react@"^11.0.0-rc.0" from @emotion/[email protected]
npm ERR! node_modules/@emotion/styled
npm ERR! @emotion/styled@"^11.10.5" from the root project
npm ERR! 3 more (@mui/material, @mui/styled-engine, @mui/system)
npm ERR! 3 more (@mui/material, @mui/styled-engine, @mui/system)
npm ERR! 29 more (@emotion/styled, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.1 || ^17" from [email protected]
npm ERR! node_modules/react-alert
npm ERR! react-alert@"^7.0.3" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR! peer react@"^16.8.1 || ^17" from [email protected]
npm ERR! node_modules/react-alert
npm ERR! react-alert@"^7.0.3" 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!
npm ERR! For a full report see:
npm ERR! C:\Users\spars\AppData\Local\npm-cache_logs\2023-06-15T09_11_40_854Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\spars\AppData\Local\npm-cache_logs\2023-06-15T09_11_40_854Z-debug-0.log