First option:
Run node command as:
node --max_old_space_size=8048 ./node_modules/@angular/cli/bin/ng serve
where 8048 is new memory limit in megabytes (by default it's ~1500).
Or add the command to package.json file:
"build-serve": "node --max_old_space_size=8048 ./node_modules/@angular/cli/bin/ng serve"
and run as npm run build-serve
Second option:
The quick and effective solution for Windows
Open C:\Users\userName\%AppData%\Roaming\npm
Copy/paste the following code into ng.cmd:
@IF EXIST "%~dp0\node.exe" (
"%~dp0\node.exe" --max_old_space_size=8048 "%~dp0\node_modules\@angular\cli\bin\ng" %*
) ELSE (
@SETLOCAL
@SET PATHEXT=%PATHEXT:;.JS;=;%
node --max_old_space_size=8048 "%~dp0\node_modules\@angular\cli\bin\ng" %*
)
UPD (7 May 2020)
Third option:
Set it as an environment variable.
SET NODE_OPTIONS=--max_old_space_size=8048
Thanks to @jonyadamit for sharing
Cheers!
Top comments (15)
Thanks a lot :) First option worked for me.
It worked for me too. Thanks @andreisfedotov
2023 angular 15 this solution works.
Thanks a lot :)
I don't think this is correct and only a bandaid solution for local development. CircleCI and TraviisCI have memory limits for their containers. I know CircleCI is 4GB (at least in the most common tier). I also think giving 8Gbs of swap to nodeJS is not a good idea given developers will be running other memory heavy applications (IDE, Browser etc.. ) and most developers (if lucky) will have 16GBs of memory.
Just to clarify, the
max_old_space_sizelimit the amount of memory used for the process. So in CI environements (like BitBucket, Travis CI, etc) you can use this configuration to avoid use more than that. Instead of setting 8Gbs or 12Gb set ony the maximum your environment allows 4Gb for most common CI. This solved an issue with Angular after upgrating to version 14.This helps me a lot. Thanks a lot!
i.e. 1st option worked for me.
You're a life-saver! Thanks!
Welldone, I just run this command in CMD "node --max_old_space_size=8048 ./node_modules/@angular/cli/bin/ng serve" And it's work for me :-)
Thanks man, it helps me a lot...!
Thanks!
Option #3: Set it as an environment variable.
SET NODE_OPTIONS=--max_old_space_size=8048
Thanks for sharing! I added it into the note.
You are the master indeed !
Thanks a lot.
Thanks man!
2nd option helps me a lot.
It works now.
:)
Why this error is come ?
what is root couse of this error?
The root of this problem lies in the insufficient amount of allocated memory for the application. This can happen when, for example, an application is quite large like an enterprise application. And there is not able to specify the heap allocation size with the help of
ngcommand. However Node can be used not only to serve the application but also to perform such things like allocating more memory to the app.