-
Notifications
You must be signed in to change notification settings - Fork 977
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Angular Google Maps (@agm/core) - Unexpected token export #171
Comments
Any insight into this? |
Hey @Alucardz! So sorry about my delay here, the past week or so has been nuts 😅 It looks like this is actually a problem with the package itself — specifically it doesn't have a main field that points to its CJS bundle. Instead, if you import Lmk if that works for ya or if you run into any other troubles! |
Wow that's awesome, kudos for the amazing platform and superb support! |
Would there be any reason that 2 UMD modules included together, for example:
along with:
would cause the same error but on BOTH umd files?
The way I'm reasoning about it is that the snazzy-info-window.umd.js file is referencing the non-UMD version of the agm/core... which is what is breaking the whole thing, right? |
@Alucardz yup you're totally right about this — I think I've figured out a way to fix this from happening :) I've got it running locally right now but need to do some more testing before I send it to prod, shooting to have it on prod tmrw 😅 So sorry about the inconvenience!! |
@EricSimons It's working marvelously now, looks like you pushed the fix to prod :) Kudos to you sir! |
Not working for me... I'm getting this: |
This is happening again, does anyone have a solution? |
Getting the following error when testing simple example from https://angular-maps.com/guides/getting-started/ :
Can test here: https://angular-google-maps-example.stackblitz.io
Could this be related to #131 ? Although I'm not using AngularFire2 in the above example.
Could possibly be related to sebholstein/angular-google-maps#1052 even though this is a more Angular Universal issue...
The text was updated successfully, but these errors were encountered: