adrianhajdin / project_mern_memories

This is a code repository for the corresponding video tutorial. Using React, Node.js, Express & MongoDB you'll learn how to build a Full Stack MERN Application - from start to finish. The App is called "Memories" and it is a simple social media app that allows users to post interesting events that happened in their lives.
https://youtube.com/playlist?list=PL6QREj8te1P7VSwhrMf3D3Xt4V6_SRkhu
5.01k stars 1.84k forks source link

npm ERR! Could not resolve dependency: peer react@"^16.8.0 || ^17.0.0" from @material-ui/core@4.12.4 #176

Open AAdewunmi opened 11 months ago

AAdewunmi commented 11 months ago

This post is for anyone who encounters the same issue.

Ran npm install @material-ui/core at console

Got the following output:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: client@0.1.0
npm ERR! Found: react@18.2.0
npm ERR! node_modules/react
npm ERR!   react@"^18.2.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.0 || ^17.0.0" from @material-ui/core@4.12.4
npm ERR! node_modules/@material-ui/core
npm ERR!   @material-ui/core@"*" 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.

Solved it by running npm install @material-ui/core --legacy-peer-deps

Check out the following stackoverflow post for more info:

[Could not resolve dependency error peer react@"^16.8.0 || ^17.0.0" from @material-ui/core@4.12.4](https://stackoverflow.com/questions/72596908/could-not-resolve-dependency-error-peer-react16-8-0-17-0-0-from-materia)

codefromahmad commented 10 months ago

Give it a try:

npm config set legacy-peer-deps true
npm i
ABDULHAMEED-10 commented 2 months ago

Give it a try:

npm config set legacy-peer-deps true
npm i
  1. npm config set legacy-peer-deps true
  2. npm install Results: npm ERR! Invalid Version:

npm ERR! A complete log of this run can be found in: C:\Users\Cyber World\AppData\Local\npm-cache_logs\2024-08-13T10_06_33_200Z-debug-0.log