You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For others also seeking help with this, the issue is known to plague the CLI (#1652, #2974) when projects grow beyond what many of us consider small-medium sized codebases.
As you mentioned, the fix it to set Node's heap size. This is done with node --max_old_space_size=[Space in MB] followed by whatever call you wanted to make, e.g. node --max_old_space_size=2048 ./node_modules/.bin/ng build (Credit to @hansl for that one line.)
Reacted by Alejandro, Jonathan Steele, Chris Seils and khushbu
Activity
celliott181 commentedon Nov 10, 2016
For others also seeking help with this, the issue is known to plague the CLI (#1652, #2974) when projects grow beyond what many of us consider small-medium sized codebases.
As you mentioned, the fix it to set Node's heap size. This is done with
node --max_old_space_size=[Space in MB]followed by whatever call you wanted to make, e.g.node --max_old_space_size=2048 ./node_modules/.bin/ng build(Credit to @hansl for that one line.)naveedahmed1 commentedon Nov 17, 2016
This should help #1652 (comment)
filipesilva commentedon Dec 12, 2016
Closing as dupe of #1652
angular-automatic-lock-bot commentedon Sep 6, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.