Comment 2 for bug 1863921

Thanks for this report and research, Chris! I've seen the same in VMs that don't have a lot of memory, and can confirm that explicitly setting max-old-space-size can get things working again.

Figuring out a sensible default seems difficult, so I've opted for the docs approach.

Branch here: user/sandbergja/lp1863921_ng_build_prod -- I also took the opportunity to update our install docs from `ng build --prod` to `ng build --configuration="production"` to avoid a deprecation warning.