Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Module not found: Error: Can't resolve '@agm/core/services/fit-bounds' in *

See original GitHub issue

Issue description

After doing npm i with "@agm/core": "~1.0.0-beta.6",, the following error happens while building:

ERROR in ./src/app/app.module.ngfactory.js,
ERROR in ./path/to/component.ngfactory.js,
Module not found: Error: Can't resolve '@agm/core/services/fit-bounds' in path/to/module
Module not found: Error: Can't resolve '@agm/core/services/fit-bounds' in path/to/component.

Steps to reproduce and a minimal demo of the problem

Provide FitBoundsService to a module:

import { FitBoundsService } from '@agm/core/services/fit-bounds';
@NgModule({ ..., providers: [ FitBoundsService ], ...})

Import FitBoundsService in a component:

import { FitBoundsService } from '@agm/core/services/fit-bounds';

Current behavior

Fails with previously described build errors.

Expected/desired behavior

Build should not fail.

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

“@agm/core”: “^1.0.0” or “@agm/core”: “~1.0.0-beta.6”,
“@angular/*”: “~8.1.1”

NOTE: everything works as expected if I pin @agm/core to 1.0.0-beta.6,

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:6 (1 by maintainers)

Top GitHub Comments

1reaction

randallmeekercommented, May 19, 2020

I’m seeing the same behavior on version 1.1.0

I’m trying to follow this conversion, but am a bit confused. My use case is that i’m extending AgmMap in my own class in order to achieve some functionality. This requires me to call super() with FitBoundsService