search

angular-material-extensions / google-maps-autocomplete

Autocomplete input component and directive for google-maps built with angular and material design |
https://angular-material-extensions.github.io/google-maps-autocomplete
MIT License
169 stars 60 forks source link

AGM Dependency depracted #323

Closed bkr32 closed 2 years ago

bkr32 commented 3 years ago

Bug Report or Feature Request (mark with an x)

- [x] bug report -> please search issues before submitting
- [x] feature request

It seems like AGM has been deprecated and is no longer being maintained latest version being 3.0.0-beta.0 published over a year ago.

A alternative could be to use https://github.com/angular/components/tree/master/src/google-maps#readme

ryancraigmartin commented 2 years ago

@bkr32 Unfortunately it doesn't look like angular has added a places autocomplete component of their own. What alternative are you using now? https://github.com/angular/components/blob/master/src/google-maps/README.md#components The @agm/core dependency is also causing issues when trying to upgrade a project from Angular 12 to 13.

LeLunZ commented 2 years ago

@ryancraigmartin this seems to be a somewhat maintained package: https://github.com/ng-maps/ng-maps

AnthonyNahas commented 2 years ago

there is nothing to update actually on agm core since it's only a bridge between angular and google maps API

cfficaurzua commented 5 months ago

i got this error while npm i

npm ERR! node_modules/@angular/common
npm ERR!   @angular/common@"^17.3.0" 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!   peer @agm/core@"^3.0.0-beta.0" from @angular-material-extensions/google-maps-autocomplete@9.0.3
npm ERR!   node_modules/@angular-material-extensions/google-maps-autocomplete
npm ERR!     @angular-material-extensions/google-maps-autocomplete@"^9.0.3" 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! 
npm ERR! For a full report see:
npm ERR! C:\Users\username\AppData\Local\npm-cache\_logs\2024-03-15T19_57_32_379Z-eresolve-report.txt