unable to resolve dependency tree error for creating new angular project

Question

so today I wanted to create a new Angular project using the command ng new <projectname> and I got this error:

npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/jasmine-core
npm ERR!   dev jasmine-core@"~3.6.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer jasmine-core@">=3.7.1" from [email protected]
npm ERR! node_modules/karma-jasmine-html-reporter
npm ERR!   dev karma-jasmine-html-reporter@"^1.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.

I literally tried everything, I updated npm, installed Angular cli again, download and installed node again, npm audit, and a lot of other things but nothing happened.

Also as you can see error told me to use the command with --force, I tried but nothing happened, and with --legacy-peer-deps, I get the error as unknown option.

What is bothering me the most is that everything was working completely right last night and I changed nothing at all but suddenly I'm getting this error today.

Just update the angular-cli at first then ng new appName this worked for me — Gabriela Rudarska
– Gabriela Rudarska, Commented May 25, 2021 at 10:11

Community · Accepted Answer · 2021-10-06 09:26:50Z

360

Open the folder you create with ng new and open the package.json file. In devDependencies change the version of "jasmine-core" 3.6.0 to 3.8.0 and "karma-jasmine-html-reporter" from 1.7.0 to 1.6.0 and save it. Then go back to Terminal and go to your project and run npm install. Now it works and you can run ng serve.

Edit 2021

"jasmine-core": "~3.8.0",
"karma-jasmine-html-reporter": "^1.7.0"

edited Oct 6, 2021 at 9:26

CommunityBot

11 silver badge

answered May 8, 2021 at 9:53

David Öztürk

3,6241 gold badge6 silver badges7 bronze badges

Sign up to request clarification or add additional context in comments.

11 Comments

kshetline Over a year ago

I've been having this problem for a while, but I was already at jasmine-core 3.7.1. Instead, I had to use npm i --legacy-peer-deps to get anywhere. Today I found jasmine-core 3.8.0 available, and that finally fixes the problem for me.

reads0520 Over a year ago

Any idea if this is something that can be changed/fixed on my end to prevent this, or is it a cli bug? Pretty bad when you have to google workarounds just to create an Angular hello world project.

afe Over a year ago

Still working in 2022

Hazem HASAN Over a year ago

It works form me, thanks, but I think that errors like that are not accepatable :)

moueza Over a year ago

It is really a shame to get an error, you are no responsible of, at the start of a project ! And really horrible for beginners !

|

Iogui · Accepted Answer · 2022-05-06 17:40:02Z

41

Mine is a temporary solution for angular-cli v11.2.12 based on @david-Öztürk answer and on this angular-cli github issue discussions and on its merged fix.

By executing the steps listed on @david-Öztürk answer I was still getting the same error. And also the fix is more conservative than the proposed solution. I hope it helps someone else:

Run the Angular project creation without automatic npm packages installation:

ng new --skip-install <project-name>

Enter project directory:

cd <project-name>

Edit package.json and change this...

"karma-jasmine-html-reporter": "^1.5.0",

...to this:

"karma-jasmine-html-reporter": "~1.5.0",

Manually install npm packages:

npm install

Note: The version 1.5.0 here was used because it is the version that appears in the error message and we are tying to be more conservative here. Please adapt the version according to your specific necessity. For newer projects the version 1.7.0 may be more suited but it can change with time. Read your specific error message in order to chose what better addresses your specific case.

edited May 6, 2022 at 17:40

answered May 12, 2021 at 19:37

Iogui

1,7281 gold badge21 silver badges34 bronze badges

3 Comments

Ian Poston Framer Over a year ago

adding the "~" to 1.5.0 worked for me. I am updated to angular version 12.2.4. I had to throw out my package-lock.json first. a silly workaround but what you gonna do. thanks Iogui!

Iogui Over a year ago

@IanPostonFramer I belive that if you run npm install after manually changing your package.json file it updates your package-lock.json for you. Anyway, the first step with the --skip-install flag should not generate a package-lock.json avoiding this problem.

Sahil Singh Over a year ago

stackoverflow.com/a/25861938/981766

Maxime GH · Accepted Answer · 2021-05-11 18:59:14Z

21

I had the same problem and I solved it with reinstalling nodeJs 14.16.1 but I had to change the version of npm manually with the command

npm install -g [email protected]

After of course, I tested the modifications by creating a project

ng new <MyProjet>

answered May 11, 2021 at 18:59

Maxime GH

6347 silver badges8 bronze badges

1 Comment

Nandini Ashok Tuptewar Over a year ago

Its absolutely right.Issue was due to package version.

MBB · Accepted Answer · 2021-05-08 19:38:12Z

9

Looks like the issue with latest NPM 7.12.0 and the latest Node 16.1.0(Current Version)

In my case I followed the below steps -

Uninstall Node
Re-Install the Latest Node (LTS: 14.16.1)
- Which will install the latest NPM : 6.14.12
Run the ng new my-app

answered May 8, 2021 at 19:38

MBB

1,6954 gold badges11 silver badges21 bronze badges

2 Comments

Ryan Loggerythm Over a year ago

thanks! works like a charm. I use nvm, so my steps were: "nvm install --lts" then reinstall angular "npm install -g @angular/cli" and it worked perfectly

Ali Khakpouri Over a year ago

This solution is perfect. Just remember to remove the npm and node folders from %userprofile%/AppData/Roaming after running the uninstall step. This way you can be sure that you've fully deleted node & npm.

Prashant Rajput · Accepted Answer · 2021-07-12 21:16:40Z

9

If you are still facing this problem then try to make sure your package.json have all versions matching other supporting library versions. The jasmine-core had to be greater than 3.8 with karma-jasmine-html-report 1.7+

here is how my devDependecies looked inside package.json

"devDependencies": {
    "@angular-devkit/build-angular": "~12.0.0",
    "@angular/cli": "~12.0.0",
    "@angular/compiler-cli": "~12.0.0",
    "@types/jasmine": "~3.6.0",
    "@types/node": "^12.11.1",
    "jasmine-core": "~3.8.0",
    "karma": "~6.3.0",
    "karma-chrome-launcher": "~3.1.0",
    "karma-coverage": "~2.0.3",
    "karma-jasmine": "~4.0.0",
    "karma-jasmine-html-reporter": "^1.7.0",
    "typescript": "~4.2.3"
  }

answered Jul 12, 2021 at 21:16

Prashant Rajput

1611 silver badge3 bronze badges

Comments

Jeyson Mg · Accepted Answer · 2022-01-26 16:16:21Z

8

What it worked for me was manually update package.json to look like this

"jasmine-core": "~3.8.0",
"karma-jasmine-html-reporter": "^1.7.0"

and then I tried

npm install

but didn't work either so I tried

npm install --legacy-peer-deps

and then everything worked again I was able to do npm start as usual

answered Jan 26, 2022 at 16:16

Jeyson Mg

1601 silver badge7 bronze badges

Comments

Caesarius · Accepted Answer · 2021-05-30 03:06:26Z

5

install node, if you do not have it or update to the newest version: https://nodejs.org/en/download/package-manager/

update your npm: npm install npm@latest -g

optional : npm i update-node

This will update angular to its newest version: npm install -g @angular/cli Create a new angular project: ng new projectName Change directory the projectName: cd projectName Serve the project ng s

edited May 30, 2021 at 3:06

answered May 30, 2021 at 2:53

Caesarius

1091 silver badge5 bronze badges

Comments

Mateusz Poreba · Accepted Answer · 2021-10-10 10:25:56Z

5

You can update angular cli globally: npm update @angular/cli -g

answered Oct 10, 2021 at 10:25

Mateusz Poreba

791 silver badge3 bronze badges

1 Comment

Jamo Over a year ago

This is the simplest way to do this.

MBB · Accepted Answer · 2021-05-12 05:45:15Z

4

They have released Karma Jasmine html reporter few hours ago. This maybe what is breaking the code. The update is most likely the cause.

You should change the package.json and get the older version of the Karma Jasmine older version

edited May 12, 2021 at 5:45

MBB

1,6954 gold badges11 silver badges21 bronze badges

answered May 8, 2021 at 0:00

NoviceDeveloper

1,2903 gold badges18 silver badges43 bronze badges

Comments

Rahul Sharma · Accepted Answer · 2021-05-23 15:53:39Z

1

I solved this issue by using this command inside my project directory:

npm install --save-dev @angular-devkit/build-angular --force
npm audit fix --force

then I ran my project using "ng serve"

edited May 23, 2021 at 15:53

answered May 12, 2021 at 14:47

Rahul Sharma

816 bronze badges

Comments

Lorenzo Dimitri Bono · Accepted Answer · 2021-07-15 16:26:12Z

1

Edit the package.json in your project folder.

"jasmine-core": "~3.7.0" to "jasmine-core": "~3.8.0", "karma-jasmine-html-reporter": "^1.5.0" to "karma-jasmine-html-reporter": "^1.6.0"

After run npm install in your project folder.

answered Jul 15, 2021 at 16:26

Lorenzo Dimitri Bono

535 bronze badges

Comments

manishnitte · Accepted Answer · 2021-05-14 11:25:34Z

0

Error Details after doing ng new my-app

npm ERR! Could not resolve dependency:

npm ERR! peer jasmine-core@">=3.7.1" from [email protected]

Fix Details

sudo npm install -g [email protected] => updated npm from 7.10.0 to 7.13.0
Only changed "jasmine-core" from 3.6.0 to 3.7.1 i.e "jasmine-core": "~3.7.1", in package.json
npm install

After this found no issues and I was able to do ng build and ng serve.

Other settings I left as it was : "@types/jasmine": "~3.6.0", "jasmine-spec-reporter": "~5.0.0",

edited May 14, 2021 at 11:25

answered May 14, 2021 at 11:18

manishnitte

2113 silver badges10 bronze badges

Comments

bmi · Accepted Answer · 2021-09-24 08:25:46Z

0

Does not help update npm nor node.js. Strange error, strange error mesages. Does help to update package.json - change version of something 'jasmine' - "jasmine-core": "~3.8.0". I don't know what is it for, but it make problems.

answered Sep 24, 2021 at 8:25

bmi

8413 gold badges12 silver badges19 bronze badges

Comments

Binyamin Regev · Accepted Answer · 2022-03-05 23:02:24Z

I encountered this issue today, after updating npm to latest - currently 8.5.3. THen I simply run ng new <my-new-project> from command-line, adding Angular Route I answered y, and selected SCSS. ng did his thing and I got the error, only different versions:

Angular 12

No jasmine-core - In the error states "[email protected]" and I need "jasmine-code@>=3.8")
No karma-jasmine-html-reporter (error states "@^1.5.0" and I need "@1.7.0")
Checked node_modules and packages.json- no mention, nor trace, of those.

After reading this issue and answers. I decided to update my Angular to the latest and run ng -g i angular-cli@latest and I received an error that the file ng.cmd already exists in folder {Windows-users-username-folder}\AppData\Roaming\npm\ng.cmd - I deleted the file. The 2nd time I run the update of Angular I received the same error on file ng. (deleted it) and the 3rd time the error was on ng.ps1 (deleted it three). Then update of Angular was successful. Then I run ng new <my-new-project> and it was successful as well.

By the way, in my new project's packages.json I see:

"devDependencies": {
    "@angular/compiler-cli": "^2.3.1", 
    "@types/jasmine": "2.5.38", 
    "@types/node": "^6.0.42",
    "angular-cli": "1.0.0-beta.28.3",
    "codelyzer": "~2.0.0-beta.1",
    "jasmine-core": "2.5.2",
    "jasmine-spec-reporter": "2.5.0",
    "karma": "1.2.0",
    "karma-chrome-launcher": "^2.0.0",
    "karma-cli": "^1.0.1",
    "karma-jasmine": "^1.0.2",
    "karma-remap-istanbul": "^0.2.1",
    "protractor": "~4.0.13","ts-node": "1.2.1", "tslint": "^4.3.0", 
    "typescript": "~2.0.3"
}

Nothing even remotely similar to what was stated in the error.

LongDev · Accepted Answer · 2024-01-06 08:21:45Z

0

you can try on this

 npx -p @angular/[email protected] --legacy-peer-deps  ng new  angular12App

answered Jan 6, 2024 at 8:21

LongDev

2473 silver badges4 bronze badges

1 Comment

Jeremy Caney Over a year ago

Thank you for your interest in contributing to the Stack Overflow community. This question already has quite a few answers—including one that has been extensively validated by the community. Are you certain your approach hasn’t been given previously? If so, it would be useful to explain how your approach is different, under what circumstances your approach might be preferred, and/or why you think the previous answers aren’t sufficient. Can you kindly edit your answer to offer an explanation?

CodeTzu · Accepted Answer · 2021-06-03 17:28:04Z

-2

If you're still experiencing this after trying some/all of the above options, Just downgrade npm version from 7 to 6: npm install -g npm@6

answered Jun 3, 2021 at 17:28

CodeTzu

656 bronze badges

Collectives™ on Stack Overflow

unable to resolve dependency tree error for creating new angular project

16 Answers 16

11 Comments

3 Comments

1 Comment

2 Comments

Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

16 Answers 16

11 Comments

3 Comments

1 Comment

2 Comments

Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Linked

Related