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

Running npm install on a freshly cloned repository fails #15021

Closed
dbaeumer opened this issue Sep 2, 2021 · 3 comments
Closed

Running npm install on a freshly cloned repository fails #15021

dbaeumer opened this issue Sep 2, 2021 · 3 comments
Labels
archived due to age This issue has been archived; please open a new issue for any further discussion bug ESLint is working incorrectly repro:needed
Projects

Comments

@dbaeumer
Copy link

dbaeumer commented Sep 2, 2021

You get

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: eslint@8.0.0-beta.1
npm ERR! Found: eslint@8.0.0-beta.1
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"file:." from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@">=5" from eslint-utils@3.0.0
npm ERR! node_modules/eslint-utils
npm ERR!   eslint-utils@"^3.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! See /home/dirkb/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/dirkb/.npm/_logs/2021-09-02T18_29_43_314Z-debug.log
@dbaeumer dbaeumer added bug ESLint is working incorrectly repro:needed labels Sep 2, 2021
@eslint-github-bot eslint-github-bot bot added this to Needs Triage in Triage Sep 2, 2021
@dbaeumer
Copy link
Author

dbaeumer commented Sep 2, 2021

Steps to reproduce:

@mdjermanovic
Copy link
Member

Some dependencies/devDependencies have ESLint as a peer dependency.

Assuming that you're using Node 16, you'll have to use --force or --legacy-peer-deps flag when installing a beta version, because "8.0.0-beta.1" doesn't satisfy requirements such as "eslint": ">=5".

We set npm install --force in our CI (ref #14933).

@dbaeumer
Copy link
Author

dbaeumer commented Sep 3, 2021

@mdjermanovic thanks !

@dbaeumer dbaeumer closed this as completed Sep 3, 2021
Triage automation moved this from Needs Triage to Complete Sep 3, 2021
@eslint-github-bot eslint-github-bot bot locked and limited conversation to collaborators Mar 3, 2022
@eslint-github-bot eslint-github-bot bot added the archived due to age This issue has been archived; please open a new issue for any further discussion label Mar 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
archived due to age This issue has been archived; please open a new issue for any further discussion bug ESLint is working incorrectly repro:needed
Projects
Archived in project
Triage
Complete
Development

No branches or pull requests

2 participants