Skip to content
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

ERROR in Maximum callstack size exceeded when building in production mode in Angular 5.2.9 #38

Open
phillips-tech opened this issue Apr 10, 2018 · 9 comments

Comments

@phillips-tech
Copy link

I'm submitting a...


[x] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/psykolm22/angular-google-place/blob/master/CONTRIBUTING.md#question

Current behavior

ng build --aot fails with "ERROR in Maximum call stack size exceeded" after npm install angular-google-place and add import {AngularGooglePlaceModule} from 'angular-google-place'; to app.module.ts of brand new Angular app.

Expected behavior

aot build should be successful?

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment


Angular Google place version : 0.0.3

output from ng -v:

Angular CLI: 1.7.4
Node: 8.10.0
OS: win32 x64
Angular: 5.2.9
... animations, common, compiler, compiler-cli, core, forms
... http, platform-browser, platform-browser-dynamic, router

@angular/cli: 1.7.4
@angular/material: 5.2.4
@angular-devkit/build-optimizer: 0.3.2
@angular-devkit/core: 0.3.2
@angular-devkit/schematics: 0.3.2
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 1.10.2
@schematics/angular: 0.3.2
@schematics/package-update: 0.3.2
typescript: 2.4.2
webpack: 3.11.0

Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
For Tooling issues:
- Node version: XX  
- Platform:  

Others:

@clarkmclean
Copy link

We're having the same issue.

Node: 6.10.3
OS: darwin x64
Angular: 5.2.10
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router

@angular/cdk: 5.2.5
@angular/cli: 1.7.4
@angular/material: 5.2.5
@angular-devkit/build-optimizer: 0.3.2
@angular-devkit/core: 0.3.2
@angular-devkit/schematics: 0.3.2
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 1.10.2
@schematics/angular: 0.3.2
@schematics/package-update: 0.3.2
typescript: 2.4.2
webpack: 3.11.0```

@nikhil271995
Copy link

Same Issue

Angular CLI: 1.7.4
Node: 9.10.1
OS: linux x64
Angular: 5.1.2
... animations, common, compiler, core, forms, http
... platform-browser, platform-browser-dynamic, platform-server
... router

@angular/cdk: 5.2.5
@angular/cli: 1.7.4
@angular/compiler-cli: 5.2.11
@angular-devkit/build-optimizer: 0.3.2
@angular-devkit/core: 0.3.2
@angular-devkit/schematics: 0.3.2
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 1.10.2
@schematics/angular: 0.3.2
@schematics/package-update: 0.3.2
typescript: 2.9.2
webpack: 3.11.0

@nsksaisaravana
Copy link

nsksaisaravana commented Jun 28, 2018

I am also having the same issue.

image

@kumaresantechin
Copy link

Any one solved this issue?

@tdubuffet
Copy link

+1

2 similar comments
@nyahyaoui
Copy link

+1

@kublaios
Copy link

+1

@kublaios
Copy link

I have -temporarily- worked this around by using this solution: #29 (comment)

@MattStrybis
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants