NG 14 support not published

[aotaduy]

Hi
We are users of this package but we need to upgrade to angular 14.
Looks like the required changes are merged but not published to npm.
Could you please publish the latest changes to npm creating a new version so we can update this dependency ?

Regards!

[Juliete]

I need it too, I'm doing my npm install with --force

[jncalderon]

@sebholstein I need it too :)

[ghost]

Same for me :/

[keithcoughtrey]

And another

[broomfn]

+1

[jncalderon]

@sebholstein need help ? here are people interest in add support to NG14, your project is very valuable and helpful

[madmacc]

I just upgraded to Angular 16. Any plans for that?
I'm looking at changing to https://www.npmjs.com/package/@angular/google-maps or https://github.com/ng-maps/ng-maps
Pros and cons vs waiting?

[DaSchTour]

@jncalderon if you would like to help I would like to invite to help with https://github.com/ng-maps/ng-maps
I started it as an organization to have a fork of AGM that can be maintained by more than one person and that will have a workflow to publish updates not depending on one developer.

[aotaduy]

Hi Everyone,
We have created a fork of this repo (https://github.com/grupo-san-cristobal/angular-google-maps/tree/develop) to publish a full compatible version, with Angular 14 support, we are going to also publish an Angular 15 compatible version in the near future.

We dont plan on changing any API from the original project, only angular migrations and bug fixing.

We are using this package in some commercial projects and plan to support it long term. Our idea is to contribute back to the original repo, but we tried to contact @sebholstein with no luck yet.

We have created the repo and published the Angular 14 packages here:

https://www.npmjs.com/package/@grupo-san-cristobal/agm-core
https://www.npmjs.com/package/@grupo-san-cristobal/agm-drawing
https://www.npmjs.com/package/@grupo-san-cristobal/agm-markerclusterer
https://www.npmjs.com/package/@grupo-san-cristobal/agm-snazzy-info-window

Feel free to use them we have tested core and drawing that are the ones we use in our applications, but the others should work fine.

[DaSchTour]

I'm really curious how this is a good idea to create numerous forks. While maintaining one was already hard as you can see by this discussion and you already struggle to keep yours up to date with latest angular.

[broomfn]

Thanks for stepping up @aotaduy, in the end we removed this package in favour of one with a larger user base and better supported.

[DaSchTour]

Thanks for stepping up @aotaduy, in the end we removed this package in favour of one with a larger user base and better supported.

Just out of curiosity, would let us know which package you switch to, which has a larger user base and better support?

[broomfn]

Thanks for stepping up @aotaduy, in the end we removed this package in favour of one with a larger user base and better supported.

Just out of curiosity, would let us know which package you switch to, which has a larger user base and better support?

Sure, I'm not sure how useful it will be to you, I suppose it depends what kind of project you have, but we switched to https://www.npmjs.com/package/@capacitor/google-maps for use in an Ionic App.

[madmacc]

Curious why people would not use https://www.npmjs.com/package/@angular/google-maps now that it is an official Angular component?
I'm planning on moving to this.

[madmacc]

Thanks for stepping up @aotaduy, in the end we removed this package in favour of one with a larger user base and better supported.

Just out of curiosity, would let us know which package you switch to, which has a larger user base and better support?

Sure, I'm not sure how useful it will be to you, I suppose it depends what kind of project you have, but we switched to https://www.npmjs.com/package/@capacitor/google-maps for use in an Ionic App.

I will also use this for my Ionic app.