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

ng8 build fails with JavaScript heap out of memory #1771

Closed
katyapavlenko opened this issue Dec 18, 2019 · 3 comments
Closed

ng8 build fails with JavaScript heap out of memory #1771

katyapavlenko opened this issue Dec 18, 2019 · 3 comments
Labels
closed:stale Issue or PR has not seen activity recently

Comments

@katyapavlenko
Copy link

katyapavlenko commented Dec 18, 2019

I have added Auth0Lock to my ng8 project and it started failing on build

  node v10.16.0 
  npm v6.9.0,
  auth0-lock: 11.2.3,
  @angular/core: 8.2.3,
  typescript: 3.5.3,

If I run
ng build without minified option, I get error

{ Error: Command failed: ng build --prod --configuration=config --output-path=test --base-href=/test/
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

If build is minified – everything is ok

  import Auth0Lock from 'auth0-lock'

  // this code causes an error
  this.lock = new Auth0Lock(
     'abc',
     'https://localhost:4200',
      options
    )

There is a discussion of similar error in angular repo, and the only solution is to increase memory. I can do it, but it's not a desired solution. I have found that Autn0Lock package causes this problem in my case, so assume something may be fixed inside of it.
By the way with ng5 or on node 12.13 everything operating ok
angular/angular-cli#13734

@stevehobbsdev
Copy link
Contributor

With regards to ng5, if the only thing you're changing is switching to ng8 then it suggests something about that isn't compatible. Let's wait and see the outcome of the issue you linked before acting. Could you report back here once there are some more concrete findings?

@katyapavlenko
Copy link
Author

Ok, I'd update this issue if would find something out

@stale
Copy link

stale bot commented Mar 17, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you have not received a response for our team (apologies for the delay) and this is still a blocker, please reply with additional information or just a ping. Thank you for your contribution! 🙇‍♂️

@stale stale bot added the closed:stale Issue or PR has not seen activity recently label Mar 17, 2020
@stale stale bot closed this as completed Mar 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed:stale Issue or PR has not seen activity recently
Projects
None yet
Development

No branches or pull requests

2 participants