set NODE_OPTIONS variable

[RayGuo-ergou]

The command to set NODE_OPTIONS variable is vary due to the OS, e.g. linux uses export but windows uses set. So the current script "serve:angular13": "export NODE_OPTIONS=--max_old_space_size=4096&& ng serve --host 0.0.0.0", would not work on windows.

[RayGuo-ergou]

Found a solution from this post that uses node to set the NODE_OPTIONS. node --max-old-space-size=8192 index.js, for angular project could be "build-prod": "node --max-old-space-size=8192 ./node_modules/@angular/cli/bin/ng build --configuration=production".

[tancnle]

@RayGuo-ergou Just circling back to this issue, could you confirm that this happens on Powershell on Windows? How about WSL or Git Bash on Windows?

[RayGuo-ergou]

PowerShell:

GitBash:

WSL would be fine as it just linux (Full Linux kernel in WSL2) and I used for all my tasks/PR reviews.

@tancnle

[tancnle]

I am wondering if we just stick with WSL2 for the Windows setup. The maintenance cost for other shells such as Powershell might not be worth it. What do you think?

I am keen to hear your thoughts as well @macite @jakerenzella 🙏🏼

[maddernd]

@tancnle I think this can be closed now as we are running in a dev container and this does not seem to be an issue any more.

@macite

[tancnle]

Thank you for the ping @maddernd. I think that's ok to close. However, if we don't support running on local machine without container, we should update the README to reflect that.