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

[Bug] Error while running npm install #394

Open
felipeemsabino opened this issue Oct 6, 2021 · 7 comments
Open

[Bug] Error while running npm install #394

felipeemsabino opened this issue Oct 6, 2021 · 7 comments

Comments

@felipeemsabino
Copy link

felipeemsabino commented Oct 6, 2021

Version

2.6.0

Reproduction link

https://

Operating System

Linux Ubuntu

Device

Desktop

Browser & Version

Google Chrome Versão 92.0.4515.107 64 bits

Steps to reproduce

  1. Download the material theme at https://demos.creative-tim.com/material-dashboard-pro-angular2/#/documentation/tutorial
  2. Go to the project root folder and run npm install

What is expected?

Install all project dependencies without error

What is actually happening?

npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: @angular/[email protected]
npm ERR! node_modules/@angular/common
npm ERR! @angular/common@"12.1.2" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^6.0.0 || ^7.0.0 || ^8.0.0" from @agm/[email protected]
npm ERR! node_modules/@agm/core
npm ERR! @agm/core@"1.1.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/aigo/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/aigo/.npm/_logs/2021-10-06T13_33_39_179Z-debug.log


Solution

npm install --legacy-peer-deps (Using legacy deps doesn't looks good)

Additional comments

@rarestoma
Copy link
Contributor

Hi @felipeemsabino,

Thank you for working with our products.

Can you please tell me what versions of npm and node are you using? I tested it with npm v6.14.12 and node v14.16.1 and it works fine.

Thank you,
Rares

@danilolopesabreu
Copy link

it's the same for me:
npm -v -> 8.1.4
node -v -> v16.13.0

@dprutkevich
Copy link

Hi @felipeemsabino,

Thank you for working with our products.

Can you please tell me what versions of npm and node are you using? I tested it with npm v6.14.12 and node v14.16.1 and it works fine.

Thank you, Rares
npm -v -> 8.1.2
node -v -> v16.13.0

The same for me.

@danilolopesabreu
Copy link

Hi @dprutkevich , thanks for the reply, making downgrade to node v14 i can install the dependencies.

@Truper63
Copy link

I am using NODE version 16.13.2 and NPM version 7.21.0. Is there a fix for the error that felipeemsabino originally reported? I do not want to downgrade my NODE version.

It seems I can never use your products because they are always behind.

@rarestoma
Copy link
Contributor

Hi @Truper63,

Can you please update your project with the following package.json?
package.json.zip

Thank you,
Rares

@Truper63
Copy link

Truper63 commented Feb 11, 2022 via email

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

5 participants