tag:help.appveyor.com,2012-11-13:/discussions/problems/13669-fork-ts-checker-webpack-plugin-triggers-javascript-heap-out-of-memoryAppVeyor: Discussion 2018-10-19T08:18:44Ztag:help.appveyor.com,2012-11-13:Comment/450756512018-04-11T16:54:07Z2018-04-11T16:54:07Zfork-ts-checker-webpack-plugin triggers JavaScript heap out of memory<div><p>Look at the similar thread here: <a href="https://help.appveyor.com/discussions/problems/11981-fatal-error-call_and_retry_last-allocation-failed-javascript-heap-out-of-memory">https://help.appveyor.com/discussions/problems/11981-fatal-error-ca...</a></p>
<p>Wondering if the solution there can help you; otherwise we can put your account on GCE where VMs have more RAM: <a href="https://www.appveyor.com/docs/build-environment/#google-compute-engine">https://www.appveyor.com/docs/build-environment/#google-compute-engine</a></p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/450756512018-04-11T18:14:54Z2018-04-11T18:14:54Zfork-ts-checker-webpack-plugin triggers JavaScript heap out of memory<div><p>Trying it now. I also found I could reduce the memory used by the plugin, which appeared to work, though it slows our local builds down.</p></div>ryantag:help.appveyor.com,2012-11-13:Comment/450756512018-04-16T15:47:29Z2018-04-16T15:47:29Zfork-ts-checker-webpack-plugin triggers JavaScript heap out of memory<div><p>The links above did not work, but setting a memory limit on the plugin to 1024 did work.</p></div>ryan