Should I use the HEAP error work around as a permanent solution?

Viewed 35

My project is now throwing this exact HEAP message when trying to run GULP to build out the UI:

HEAP ERROR

This question here deals with this issue: Node.js heap out of memory

I do not know why it is all of a sudden throwing this error. The application is a mature application (Angular 8, .NetFramework 4.7, NODE v16.14.2). Everything has been going fairly well until we just got this error.

In my research, I've seen a lot of: "just add this to your environment variable..."

NODE_OPTIONS="--max-old-space-size=8192"

I have validated that I no longer get this HEAP error during the GULP process when I apply the environment variable fix but, is this really the answer? What ramifications are there by using the NODE-OPTIONS environment variable fix (NODE_OPTIONS="--max-old-space-size=8192")? Will I have to apply this to our build servers? What happens when this overflows and I need to increase it yet again?

Does this seem like the right course of action?

0 Answers
Related