If there are many big JS files to be parsed by the JS parser in the SBG, it may fail with V8 Out-of-Memory exception. This happens rarely but, still, there might be a problem with the default webpack flow.
The JS parser in the SBG is ran as a Node process and if it is not started with a max heap size flag it uses V8's default heap size which is around 1.7gb.
We should start the Node process with a bigger available amount of memory but still allow users to provide the NODE_OPTIONS environment variable to manually change the Node configs.
If there are many big JS files to be parsed by the JS parser in the SBG, it may fail with V8 Out-of-Memory exception. This happens rarely but, still, there might be a problem with the default webpack flow.
The JS parser in the SBG is ran as a Node process and if it is not started with a max heap size flag it uses V8's default heap size which is around 1.7gb.
We should start the Node process with a bigger available amount of memory but still allow users to provide the
NODE_OPTIONSenvironment variable to manually change the Node configs.