-
Notifications
You must be signed in to change notification settings - Fork 820
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
Comments
You can skip peer dependency conflicts checking by running More information: https://blog.npmjs.org/post/626173315965468672/npm-v7-series-beta-release-and-semver-major |
Hi, try |
@blondie63 it's unrelated. You have to update npm to 7.5.6 or newer to match |
Is there a plan to update the package for compatibility with Angular 11? Looks like this PR might be doing it? #1919 |
@JoeOsterfeld It seems that this repository was abandoned and not maintained any more |
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. |
Any update on this, having the same issue
|
@mikende You can use this library instead: @angular/google-maps |
I just updated my npm for Angular less then 11 to this version 7.5.6 and npm run build is working. |
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. |
Works perfect for me!!!... realy thnx |
What's the sense of having a package which is not working?????? |
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
The text was updated successfully, but these errors were encountered: