Angular-google-maps: @agm/[email protected] has incorrect peer dependency with Angular 9

Created on 15 Apr 2020  路  6Comments  路  Source: SebastianM/angular-google-maps

Issue description
Build gets the following warnings:

warning " > @agm/[email protected]" has incorrect peer dependency "@angular/common@^6.0.0 || ^7.0.0 || ^8.0.0".
warning " > @agm/[email protected]" has incorrect peer dependency "@angular/core@^6.0.0 || ^7.0.0 || ^8.0.0".
warning " > @agm/[email protected]" has incorrect peer dependency "@angular/core@^6.0.0 || ^7.0.0 || ^8.0.0".

Steps to reproduce and a minimal demo of the problem
Build @agm/[email protected] and @agm/[email protected] with Angular v9

Current behavior
Gets the above listed warnings.

Expected/desired behavior
No warnings.

angular-google-maps, Angular, & any other relevant dependency versions

Other information
Should be straightforward!

Most helpful comment

same issue here, any updates?

@agm/[email protected] requires a peer of @angular/common@^6.0.0 || ^7.0.0 || ^8.0.0 but none is installed. You must install peer dependencies yourself.
@agm/[email protected] requires a peer of @angular/core@^6.0.0 || ^7.0.0 || ^8.0.0 but none is installed. You must install peer dependencies yourself.

All 6 comments

@agm/[email protected] requires a peer of @angular/common@^6.0.0 || ^7.0.0 || ^8.0.0 but none is installed

same issue here, any updates?

@agm/[email protected] requires a peer of @angular/common@^6.0.0 || ^7.0.0 || ^8.0.0 but none is installed. You must install peer dependencies yourself.
@agm/[email protected] requires a peer of @angular/core@^6.0.0 || ^7.0.0 || ^8.0.0 but none is installed. You must install peer dependencies yourself.

Could we get any update on that?

yes, new version shoud fix it #1833

... I wouldn't close issues before the PR is even merged. The new version isn't published yet so practically the issue is still outstanding.

Don't let that comment diminish my appreciation for your fix. That PR is made up of a ton of work! Well done!

@LiandriCorp I almost agree with you, but we don't really have active maintainers atm, I am just trying to push that PR through to get some kind of compatibility in, that's why I am closing all issues that are fixed in the PR.

Also, there are probably many duplicate issues on this.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

dineshkumar20 picture dineshkumar20  路  3Comments

DeveloperAdd007 picture DeveloperAdd007  路  3Comments

Halynsky picture Halynsky  路  3Comments

gizm0bill picture gizm0bill  路  4Comments

Subhojit1992 picture Subhojit1992  路  3Comments