I am unable to get a node.js typescript project to launch properly when i npm install and when i npm run dev

133 Views Asked by At

As the title suggests i am unable to get a typescript project to launch properly and i've tried everything ive found on here.

when i use npm install i get the error message

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" from @emotion/[email protected]
npm ERR!   node_modules/@emotion/react
npm ERR!     @emotion/react@"^11.10.5" 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!       4 more (@mui/material, @mui/styled-engine, @mui/system, react-pro-sidebar)
npm ERR!     4 more (@mui/material, @mui/styled-engine, @mui/system, react-pro-sidebar)  
npm ERR!   25 more (@emotion/styled, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.0" from [email protected]
npm ERR! node_modules/react-simple-maps
npm ERR!   react-simple-maps@"^1.0.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^16.8.0" from [email protected]
npm ERR!   node_modules/react-simple-maps
npm ERR!     react-simple-maps@"^1.0.0" 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\theol\AppData\Local\npm-cache\_logs\2023-08-03T23_32_20_104Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: C:\Users\theol\AppData\Local\npm-cache\_logs\2023-08-03T23_32_20_104Z-debug-0.log`

I am able to force it using --legacy-peer-deps however when i open it in browser it gives

enter image description here

any help would be appreciated thanks.

I've tried --force, --legacy-peer-deps, i react-router-dom, npm i @types/react-router-dom non of which fixed the errors im experiencinng

after using npm install --save [email protected] [email protected] to downgrade

pm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @mui/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^16.14.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.10.5" 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!       4 more (@mui/material, @mui/system, @mui/styled-engine, react-pro-sidebar)
npm ERR!     4 more (@mui/material, @mui/system, @mui/styled-engine, react-pro-sidebar)
npm ERR!   19 more (@emotion/styled, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! node_modules/@mui/icons-material
npm ERR!   @mui/icons-material@"^5.11.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^17.0.0 || ^18.0.0" from @mui/[email protected]
npm ERR!   node_modules/@mui/icons-material
npm ERR!     @mui/icons-material@"^5.11.0" 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\theol\AppData\Local\npm-cache\_logs\2023-08-04T01_55_04_299Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: C:\Users\theol\AppData\Local\npm-cache\_logs\2023-08-04T01_55_04_299Z-debug-0.log
0

There are 0 best solutions below