Angular-google-maps: ERROR TypeError: Object(...) is not a function at new FitBoundsService after npm upgrade

Created on 24 Sep 2018 · 10Comments · Source: SebastianM/angular-google-maps

For my agm, I got the following error on my chrome browser console after npm upgrade and the page is not showing again.

Angular is running in the development mode. Call enableProdMode() to enable the production mode.
DeviceAlertComponent.html:202 ERROR TypeError: Object(...) is not a function
at new FitBoundsService (fit-bounds.js:31)
at createClass (core.js:12481)
at _createProviderInstance (core.js:12458)
at createProviderInstance (core.js:12299)
at createViewNodes (core.js:13771)
at createEmbeddedView (core.js:13661)
at callWithDebugContext (core.js:15098)
at Object.debugCreateEmbeddedView [as createEmbeddedView] (core.js:14410)
at TemplateRef_.createEmbeddedView (core.js:11736)
at ViewContainerRef_.createEmbeddedView (core.js:11448)

What could be the cause of the error?

stale

Source

kenadet

👍9

Most helpful comment

you can fix this issue instaling the previous version of the @agm/core
remove you current version : npm uninstall @agm/core
then install this version: npm i @agm/[email protected] --save

tellesdourado on 3 Oct 2018

👍23 🎉4 ❤2 😄2 🚀1

All 10 comments

I'm facing the same error since the betas 4 and 5, had to go back to beta.3 to make it work again.

JulienCapoulun on 25 Sep 2018

👍6

Faced same issue in beta.2 and beta.5. Didn't try beta.4. Working fine with beta.3

shivaramanp on 26 Sep 2018

Facing same issue even with beta.3 worked fine with beta.2

RamyaSwathi94 on 26 Sep 2018

👍1

We resolved it by removing the caret in front of 1.0.0-beta.3.

kenadet on 26 Sep 2018

👍2

Same issue. Had to go back versions. Need a fix moving forward.

joyrm on 27 Sep 2018

you can fix this issue instaling the previous version of the @agm/core
remove you current version : npm uninstall @agm/core
then install this version: npm i @agm/[email protected] --save

tellesdourado on 3 Oct 2018

👍23 🎉4 ❤2 😄2 🚀1

Same story here. Rolled back to beta3 fix it. Need fix for the future.

peterhe2000 on 24 Oct 2018

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.