Closed veneliniliev closed 5 years ago
I think this would be best to add as documentation note as it's not a general good practice to bump node heap size like, and not everyone can afford to build with 8G allocated as in your change.
I understand the need as I already had to use this trick, but I don't think it's a good default for everyone. Did you report the issue on the angular cli repo? I saw some effort on issue like this, as even on big projects it should be very rare to hit the memory limit, so it might be regression.
fixed problem for node memory limit in build real project
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory