developer-portfolio icon indicating copy to clipboard operation
developer-portfolio copied to clipboard

Dependency Conflict - react-reveal and React 17

Open BenLalor opened this issue 1 year ago • 5 comments

It appears there is a problem with the React-Reveal dependency and the latest version of React. When I try to force bypass this with: npm install --legacy-peer-deps I am unable to run npm start without failures

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@"^17.0.2" from the root project
npm ERR!   peer react@"^16.8.0 || ^17.0.0" from @material-ui/[email protected]
npm ERR!   node_modules/@material-ui/core
npm ERR!     @material-ui/core@"^4.12.2" from the root project
npm ERR!     peer @material-ui/core@"^4.0.0" from @material-ui/[email protected]
npm ERR!     node_modules/@material-ui/icons
npm ERR!       @material-ui/icons@"^4.11.2" from the root project
npm ERR!   17 more (@material-ui/icons, @material-ui/styles, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^15.3.0 || ^16.0.0" from [email protected]
npm ERR! node_modules/react-reveal
npm ERR!   react-reveal@"^1.2.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^15.3.0 || ^16.0.0" from [email protected]
npm ERR!   node_modules/react-reveal
npm ERR!     react-reveal@"^1.2.2" 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! /Users/benlalor/.npm/_logs/2024-01-02T23_29_55_280Z-eresolve-report.txt

BenLalor avatar Jan 02 '24 23:01 BenLalor

I bypassed this issue by using npm install --legacy-peer-deps with Node v 20.10.0 and the switched to node v14.x.x to run npm start

This is not ideal, broken, and should be fixed. Please advise.

BenLalor avatar Jan 03 '24 00:01 BenLalor

I just switched back fully to node v14 and that works yeah

seroteunine avatar Jan 24 '24 09:01 seroteunine

@seroteunine were you experiencing the same problem?

BenLalor avatar Jan 25 '24 21:01 BenLalor

Remove the react-reveal from package.json and run npm install to remove it completely from the project. Reinstall react-reveal using the --legacy-peer-deps flag: npm install react-reveal --save --legacy-peer-deps

puru763 avatar Jan 31 '24 19:01 puru763

Are you able to deploy? as it is giving me error while deployment.

Deepakkumarrp avatar Feb 04 '24 15:02 Deepakkumarrp