add option to set --max-old-space-size on server

[ALiangLiang]

It's a workaround to solved JavaScript heap out of memory

Motivation

I have problem on JavaScript heap out of memory. I found many related issues but many of them closed by lack of info to repro

• When using Volar in Neovim, it failed, with some failure logs #862
• "Unhandled method volar/getAttrNameCaseClient" error #658 (comment)
• server crashed 5 times in the last 3 minutes #1242 (comment)
• Volar crashes quickly using VS Code remote containers on Docker #514
• Request textDocument/hover failed when in monorepro #1025
• Potential memory leak of vue-tsc --noEmit -w #1106

$ echo "In my case"
$ NODE_OPTIONS='--max_old_space_size=700' npx vue-tsc --noEmit 
<--- Last few GCs --->

[12514:0x56b6af0]    26053 ms: Mark-sweep (reduce) 698.3 (711.3) -> 697.3 (711.1) MB, 220.5 / 0.0 ms  (average mu = 0.167, current mu = 0.156) allocation failure scavenge might not succeed
[12514:0x56b6af0]    26105 ms: Scavenge (reduce) 698.4 (711.1) -> 697.7 (711.1) MB, 5.2 / 0.0 ms  (average mu = 0.167, current mu = 0.156) allocation failure 


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
...

I tried the solutions:

1. Turn on volar.lowPowerMode: failed
2. Use take over mode: failed
3. Remove Vetur: failed
4. Set --max-old-space-size=6144 on server: success

[johnsoncodehk]

Thanks for your investigation!