#EROSOLVE could not resolve angular/common...

37 messages ยท Page 1 of 1 (latest)

viscid bridge
#

Please post the full error as text

tranquil solar
#

post the package.json also. You have uncompatible peer-deps

west tusk
#

Hello Matthieu, here is the package.son

#

Hello diesieben here is the full error :

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @agm/[email protected]
npm ERR! Found: @angular/[email protected]
npm ERR! node_modules/@angular/common
npm ERR! @angular/common@"^13.0.3" from the root project
npm ERR! peer @angular/common@"^13.0.0 || ^14.0.0-0" from @angular/[email protected]
npm ERR! node_modules/@angular/cdk
npm ERR! @angular/cdk@"^13.0.2" from the root project
npm ERR! peer @angular/cdk@"13.3.9" from @angular/[email protected]
npm ERR! node_modules/@angular/material
npm ERR! @angular/material@"^13.0.2" from the root project
npm ERR! 23 more (@angular/material, @ckeditor/ckeditor5-angular, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^9.1.0 || ^10.0.0" from @agm/[email protected]
npm ERR! node_modules/@agm/core
npm ERR! @agm/core@"^3.0.0-beta.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: @angular/[email protected]
npm ERR! node_modules/@angular/common
npm ERR! peer @angular/common@"^9.1.0 || ^10.0.0" from @agm/[email protected]
npm ERR! node_modules/@agm/core
npm ERR! @agm/core@"^3.0.0-beta.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 /opt/render/.cache/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /opt/render/.cache/_logs/2025-01-27T19_54_42_915Z-debug-0.log

#

Thank you

viscid bridge
#

peer @angular/common@"^9.1.0 || ^10.0.0" from @agm/[email protected]
This library requires Angular 9 or 10, you are trying to use Angular 13.

plush gyro
#

And also, the current version of Angular is 19. Version 13 is 3 years old.

viscid bridge
#

It also seems the package.json and the log do not match, as @agm/core does not appear in the package.json at all.

west tusk
#

Diesieben07, i uninstall it just to see if this error will still appear or not thats why its not in the package i sent

viscid bridge
west tusk
#

The error log was before i uninstall it

#

And the package.json i sent was after

viscid bridge
#

Sorry, but it is not helpful if you post unrelated information and do random things in between without telling us.

#

Please post the error log after uninstalling it.

west tusk
#

Yes sure

#

Here is my new package.json, i deleted some modules that are not supported anymore :

#

I dont get the same error anymore, npm install look like its worked but i get a whole new bunch of errors

#

I imported the modules in app.module.ts and page.module.ts and nothing seem to work

viscid bridge
#

That error is unrelated to the package.json. If the component is declared in a module, please show that module

west tusk
#

Sure

#

from page.module.ts

viscid bridge
#

ESM imports are not really relevant.

west tusk
#

And in page.module.ts also :

#

I use copilot to fix errors, but doesnt work also..

viscid bridge
#

Oh sweet lord ๐Ÿ˜„

#

Is WorkerEstimationBox component declared in that module?

west tusk
#

Yes

viscid bridge
#

The error you have shown via screenshot might just be a side effect of many other errors.
And, just a tip, Generative AI is really not good at the kind of reasoning you need to fix such errors.

west tusk
#

Yes i know i just didnt find any other solutions.. but i agree with you on this

viscid bridge
#

It's really hard to debug an error like this from afar by only looking at tiny snippets of what is obviously a big codebase with a massive list of dependencies.

west tusk
#

Can i share with you on private ?

viscid bridge
#

I guess, but no promises

west tusk
#

Thank you, hopefully someelse will have an idea about this problem..