Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

npm Install Error #48

Open
COBAcode opened this issue Jun 16, 2022 · 2 comments
Open

npm Install Error #48

COBAcode opened this issue Jun 16, 2022 · 2 comments

Comments

@COBAcode
Copy link

Hello,

When cloning the project, and after downgrading to node 16 as directed in the repo, I receive this error and cannot run npm install on the cloned repo

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/tslint
npm ERR!   dev tslint@"~6.1.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer tslint@"^3.9.0" from [email protected]
npm ERR! node_modules/codelyzer
npm ERR!   dev codelyzer@"^0.0.28" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/tslint
npm ERR!   peer tslint@"^3.9.0" from [email protected]
npm ERR!   node_modules/codelyzer
npm ERR!     dev codelyzer@"^0.0.28" 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! 

Any assistance would be appreciated.

@samaty593
Copy link

samaty593 commented Aug 27, 2022

hi, I just run into the same issue. To fix this you need to go to your package.json file and remove the "~" in front of
"tslint": "~6.1.0".

This way you're telling node that it's fine if it installs another version of tslint.

It might not be the most beautiful way to fix it but considering that it is not a core library of our application and that it is not going to make it into production we don't care much about security issues, right !?

Have a nice day.

@JayakumarrDotnet
Copy link

Hi

How to resolve this issue after npm start

error:

#60

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants