title: Should I use the HEAP error work around as a permanent solution?
body: <p>My project is now throwing this exact HEAP message when trying to run GULP to build out the UI:</p>
  <p><a href="https://i.stack.imgur.com/c1Fe5.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/c1Fe5.png" alt="HEAP ERROR" /></a></p>
  <p>This question here deals with this issue:
  <a href="https://stackoverflow.com/questions/38558989/node-js-heap-out-of-memory">Node.js heap out of memory</a></p>
  <p>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.</p>
  <p>In my research, I've seen a lot of: &quot;just add this to your environment variable...&quot;</p>
  <p><em>NODE_OPTIONS=&quot;--max-old-space-size=8192&quot;</em></p>
  <p><strong>I have validated that I no longer get this HEAP error during the GULP process when I apply the environment variable fix</strong> but, is this really the answer?  What ramifications are there by using the NODE-OPTIONS environment variable fix (NODE_OPTIONS=&quot;--max-old-space-size=8192&quot;)?  Will I have to apply this to our build servers?  What happens when this overflows and I need to increase it yet again?</p>
  <p>Does this seem like the right course of action?</p>