Angular-google-maps: Support Angular 8.0

[andlewis]

AGM has a hard dependency on old versions of Angular. Can this be upgraded?

Current error when trying to upgrade to Angular 8 is:

Package "@agm/core" has an incompatible peer dependency to "@angular/common" (requires "^5.0.0 || ^6.0.0" (extended), would install "8.0.0").
Package "@agm/snazzy-info-window" has an incompatible peer dependency to "@angular/core" (requires "^5.0.0 || ^6.0.0" (extended), would install "8.0.0").

[agil-NUBBA]

You can force the update with:

ng update @angular/cli @angular/core --force

After that you'll receive peer warnings https://github.com/SebastianM/angular-google-maps/issues/1533

[JosepAlacid]

Until then:
https://github.com/agm-preview/angular-google-maps

[nickkellerfuturedontics]

@doom777 , @JosepAlacid : We are very interested in this fork, but as this is our first time integrating a fork into an Angular project, we are curious about the best way to proceed. Any help would be greatly appreciated! If not here, then via DM on Twitter, to keep the noise down:

@nkfuturedontics

Thank you for the support and for making this fork happen!

[ghost]

ignore the fork, we are back to working on the main branch

[ghost]

close as duplicate of #1533

[anantanandgupta]

when is the release for this ... I have already moved to the @agm-preview which is now taken down, leaving all others like me stuck. you should have not removed the package until this was updated. I am not sure what was the reason for taking down the forked repository at https://github.com/agm-preview/angular-google-maps

[ghost]

@anantanandgupta you're right, we did rush removing agm-preview, but the good news is that the release for this is soon.

[evilangelmd]

@doom777 You need to provide SOLUTION first, and then take down others solution. This way was bad. Now we have a package that have no solution. Fork - down, main project without releases. great job :)

[anantanandgupta]

@anantanandgupta you're right, we did rush removing agm-preview, but the good news is that the release for this is soon.

my build server has broken ... I had a release today and my CI broke creating a headache ... what we do today ... more pressingly now ... SOON word has not timelines attached and I can't give justifications to management why the application can't be released today and more over, when we can release it?

[JosepAlacid]

@anantanandgupta I still have the corresponding @agm-preview node-module in some of my backups. If it could be of help to you, I will pleasantly send you a zip.

[anantanandgupta]

@JosepAlacid thanks for the offer but i too have the preview fork in my dev environment. It is just that my CI builds don't take it from my machine. It does a fresh npm i on a fresh dump of the code. So broken. And the deployment has to go through all the manual steps by generating the build locally and all that hell.

[ghost]

Wow, I had no idea people were actually using @agm-preview, especially in CI/ production.

I deeply apologize again for the problems I caused unpublishing.

I urgently republished @agm-preview/core so if any of you are still depending on it, it will work again.

Again, we expect @agm to publish a version real soon, so if you haven't switched yet to @agm-preview, don't.

[JosepAlacid]

I can't explain how much I appreciate people who is able to change a decision based on new information.
But If there's a way to do it, let me know @doom777.
Just as a sign of gratitude I start deleting my last comment and excusing myself...

And yes, people were using that branch as a desperate solution. Not the one it should be, but when due dates are near, frustration rings your bell. Just look at weekly downloads oft @agm-preview.

Thanks again but very much!
PD.: Maybe you had republished @agm-preview/core, but it is still not visible at GitHub...

[anantanandgupta]

@doom777 thanks for the package. And yes @JosepAlacid it was a desperate decision as we needed our application to be migrated to angular 7 and this was the only package blocking us. So as soon as I found that there is a fork enabling us to move to angular 7 we closed our eyes and took a wider step. We will move back to agm core as soon as it is available. Also i will request you all guys to make it possible for angular 8 too at the same time. Since angular 8 is out. We will not move to ng8 yet as there is another big dependency with is still behind the versioning race. But ateast there will be one less to count. Thanks again for your time and patience and above all the understanding of the need of the hour.

[ghost]

Thanks for understanding.

I published it to NPM, since that's what people were using. Were people also dependent on Github?

[anantanandgupta]

Thanks for understanding.

I published it to NPM, since that's what people were using. Were people also dependent on Github?

Not me at least ... It was actually a life saving vest.

[JosepAlacid]

Not at all! @doom777 . Just trying to fork it...

[ghost]

good news is beta.6 is out, so you can go back to @agm/core which supports angular 6, 7 and 8