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

I can't install for angular 11 #1932

Open
sergiogman opened this issue Feb 5, 2021 · 12 comments
Open

I can't install for angular 11 #1932

sergiogman opened this issue Feb 5, 2021 · 12 comments

Comments

@sergiogman
Copy link

npm i @agm/core
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: XXXX@0.0.0
npm ERR! Found: @angular/common@11.0.9
npm ERR! node_modules/@angular/common
npm ERR! @angular/common@"~11.0.5" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^9.1.0 || ^10.0.0" from @agm/core@3.0.0-beta.0
npm ERR! node_modules/@agm/core
npm ERR! @agm/core@"*" 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 \AppData\Local\npm-cache\eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR! \AppData\Local\npm-cache_logs\2021-02-05T15_13_10_410Z-debug.log

@Greenek
Copy link

Greenek commented Feb 9, 2021

You can skip peer dependency conflicts checking by running npm install --legacy-peer-deps or you can set npm config set legacy-peer-deps true and then run npm install once again.

More information: https://blog.npmjs.org/post/626173315965468672/npm-v7-series-beta-release-and-semver-major

@blondie63
Copy link

You can skip peer dependency conflicts checking by running npm install --legacy-peer-deps or you can set npm config set legacy-peer-deps true and then run npm install once again.

More information: https://blog.npmjs.org/post/626173315965468672/npm-v7-series-beta-release-and-semver-major

Hi, try npm install --legacy-peer-deps i've this:
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@angular-devkit/architect@0.1102.3',
npm WARN EBADENGINE required: { node: '>= 10.13.0', npm: '^6.11.0 || ^7.5.6', yarn: '>= 1.13.0' },
npm WARN EBADENGINE current: { node: 'v14.15.3', npm: '7.5.4' }
npm WARN EBADENGINE }

@Greenek
Copy link

Greenek commented Mar 19, 2021

@blondie63 it's unrelated. You have to update npm to 7.5.6 or newer to match @angular-devkit/architect requirements.

@JoeOsterfeld
Copy link

JoeOsterfeld commented Mar 29, 2021

Is there a plan to update the package for compatibility with Angular 11? Looks like this PR might be doing it? #1919

@sergey-morenets
Copy link

@JoeOsterfeld It seems that this repository was abandoned and not maintained any more

@stale
Copy link

stale bot commented Jul 21, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jul 21, 2021
@mikende
Copy link

mikende commented Aug 19, 2021

Any update on this, having the same issue

npm install @agm/core --save
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: lab2docx@0.0.0
npm ERR! Found: @angular/common@12.1.5
npm ERR! node_modules/@angular/common
npm ERR!   @angular/common@"~12.1.4" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^9.1.0 || ^10.0.0" from @agm/core@3.0.0-beta.0
npm ERR! node_modules/@agm/core
npm ERR!   @agm/core@"*" 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 /Users/macbookair/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/macbookair/.npm/_logs/2021-08-19T14_58_50_869Z-debug.log

@stale stale bot removed the stale label Aug 19, 2021
@sergey-morenets
Copy link

Any update on this, having the same issue

npm install @agm/core --save
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: lab2docx@0.0.0
npm ERR! Found: @angular/common@12.1.5
npm ERR! node_modules/@angular/common
npm ERR!   @angular/common@"~12.1.4" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^9.1.0 || ^10.0.0" from @agm/core@3.0.0-beta.0
npm ERR! node_modules/@agm/core
npm ERR!   @agm/core@"*" 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 /Users/macbookair/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/macbookair/.npm/_logs/2021-08-19T14_58_50_869Z-debug.log

@mikende You can use this library instead: @angular/google-maps

@TatyanaMolchanova
Copy link

@blondie63 it's unrelated. You have to update npm to 7.5.6 or newer to match @angular-devkit/architect requirements.

I just updated my npm for Angular less then 11 to this version 7.5.6 and npm run build is working.
Great thanks!

@stale
Copy link

stale bot commented Jan 9, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jan 9, 2022
@Andronico1973
Copy link

You can skip peer dependency conflicts checking by running npm install --legacy-peer-deps or you can set npm config set legacy-peer-deps true and then run npm install once again.

More information: https://blog.npmjs.org/post/626173315965468672/npm-v7-series-beta-release-and-semver-major

Works perfect for me!!!... realy thnx

@glv1at118
Copy link

What's the sense of having a package which is not working??????
import { AgmCoreModule } from '@agm/core'; // cannot find the package.
After running npm install --legacy-peer-deps, it can install, but it didn't install nothing. Checking from node_modules there's no such @agm/core package.

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

9 participants