#EROSOLVE could not resolve angular/common...
37 messages ยท Page 1 of 1 (latest)
post the package.json also. You have uncompatible peer-deps
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
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.
And also, the current version of Angular is 19. Version 13 is 3 years old.
It also seems the package.json and the log do not match, as @agm/core does not appear in the package.json at all.
Diesieben07, i uninstall it just to see if this error will still appear or not thats why its not in the package i sent
By "uninstall it" you mean what exactly? If you uninstalled it, it should not appear in the error log!
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.
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
That error is unrelated to the package.json. If the component is declared in a module, please show that module
ESM imports are not really relevant.
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.
Yes i know i just didnt find any other solutions.. but i agree with you on this
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.
Can i share with you on private ?
I guess, but no promises
Thank you, hopefully someelse will have an idea about this problem..