DEV Community

🏇 A simple tip to improve angulars compilation speed

Marcel Cremer on May 17, 2019

Do you have a large angular application that takes too long to compile / serve / compile tests? This little thing helped me: Increasing t...

Read full post

Christopher Carter • May 18 '19

I believe you can use an .npmrc file at the project level and avoid altering your scripts altogether

node-options=--max-old-space-size={{size in MB}}

Bennett Hardwick • May 18 '19

For those with computers that are packing a lot of ram, you can allow this option globally for all node applications by adding the following to your shell config:

export NODE_OPTIONS="--max_old_space_size=8096"

Iker A Saber • May 29 '19 • Edited

If you want to check how much RAM is node allocating currently, you can use this:

node -e 'console.log(v8.getHeapStatistics())'

Marcel Cremer • May 19 '19

Thank you for your input about npmrc and export guys :)

I personally don't like the export solution as it's global, but its definetly worth mentioning (for ppl who want to alter the size always).

About the .npmrc file: I honestly didn't know that it's also possible to have this on project level (only in the home folder). I'll give this one a try too.

cbolourchi • Dec 24 '19

Does anyone know how I would get this to work in Gitlab CI?

I've tried using NODE_OPTIONS in my gitlab-ci.yml and added node-options=--max-old-space-size=2048 to the .npmrc file in the project root, but whenever I do npm run-script build-prod it just reverts back to 80000 and my build never finishes on my machine. I'm using my own gitlab-runner.

I'm really at a loss.

Any help would be appreciated. Thanks.