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

error when running npm install in glee #403

Closed
KhudaDad414 opened this issue Mar 14, 2023 · 16 comments
Closed

error when running npm install in glee #403

KhudaDad414 opened this issue Mar 14, 2023 · 16 comments
Labels
area/javascript Specify what technical area given issue relates to. Its goal is to ease filtering good first issues. bug Something isn't working good first issue Good for newcomers

Comments

@KhudaDad414
Copy link
Member

Describe the bug

After cloning glee the first step is to run npm install to install the dependencies.
With the newer version of npm you will get the following error:

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/eslint
npm ERR!   dev eslint@"^8.6.0" from the root project
npm ERR!   peer eslint@"^6.0.0 || ^7.0.0 || ^8.0.0" from @typescript-eslint/[email protected]
npm ERR!   node_modules/@typescript-eslint/eslint-plugin
npm ERR!     dev @typescript-eslint/eslint-plugin@"^5.9.0" from the root project
npm ERR!     @typescript-eslint/eslint-plugin@"^5.1.0" from [email protected]
npm ERR!     node_modules/eslint-plugin-github
npm ERR!       eslint-plugin-github@"^4.3.5" from the root project
npm ERR!   15 more (@typescript-eslint/experimental-utils, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0" from [email protected]
npm ERR! node_modules/eslint-plugin-sonarjs
npm ERR!   dev eslint-plugin-sonarjs@"^0.5.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/eslint
npm ERR!   peer eslint@"^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0" from [email protected]
npm ERR!   node_modules/eslint-plugin-sonarjs
npm ERR!     dev eslint-plugin-sonarjs@"^0.5.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! 

as npm suggests adding --legacy-peer-deps resolves the issue but there should be a better solution here.
maybe a package needs to be upgraded? 🤔

How to Reproduce

  1. clone glee.
  2. run npm i with npm 8 or higher.

Expected behavior

There shouldn't be any errors and dependencies should install.

@KhudaDad414 KhudaDad414 added the bug Something isn't working label Mar 14, 2023
@asyncapi asyncapi deleted a comment from asyncapi-bot Mar 14, 2023
@KhudaDad414
Copy link
Member Author

/gfi js

@asyncapi-bot asyncapi-bot added area/javascript Specify what technical area given issue relates to. Its goal is to ease filtering good first issues. good first issue Good for newcomers labels Mar 14, 2023
@sambhavgupta0705
Copy link
Member

Hey ,I would like to look into this issue

@KhudaDad414
Copy link
Member Author

@sambhavgupta0705 sure. 🙇

@sambhavgupta0705
Copy link
Member

sambhavgupta0705 commented Mar 14, 2023

Hey @KhudaDad414 ,resolved some erros
image

I think the left one are due to conflicting dev dependencies

@sambhavgupta0705
Copy link
Member

sambhavgupta0705 commented Mar 14, 2023

I am using npm version 9.6.1 and node version 18.0.0

@KhudaDad414
Copy link
Member Author

@sambhavgupta0705 please open A PR. we can discuss this further over there :)

@sambhavgupta0705
Copy link
Member

Opening it

@SinghiHarsh
Copy link
Contributor

@KhudaDad414 I have upgraded package versions of eslint-plugin-sonarjs & typedoc
#408

@SinghiHarsh
Copy link
Contributor

SinghiHarsh commented Mar 20, 2023

Opening it

Hi @sambhavgupta0705 , I tried upgrading the package versions to fix dependency tree error,
What is your approach ?

@sambhavgupta0705
Copy link
Member

@SinghiHarsh I had the same approach of upgrading the versions.

@rukundob451
Copy link

@KhudaDad414 @sambhavgupta0705 what was the conclusion to this is it open?

@ConnectBhawna
Copy link

Hii @KhudaDad414 @sambhavgupta0705 if no one working on this i would like to work on this issue

@ayushnau
Copy link

image
cant see the issue.

@sambhavgupta0705
Copy link
Member

@ayushnau which version of npm are you using?

@Souvikns
Copy link
Member

same here, I can't reproduce the error as well I am using npm v9.7.2 and node v20.4.0

@KhudaDad414
Copy link
Member Author

tested with node v20, v18, v16 and it seems like the error doesn't show up anymore. closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/javascript Specify what technical area given issue relates to. Its goal is to ease filtering good first issues. bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

8 participants