PatrickJS-starter: webpack is really really slow and sometimes crashes with OOM

I haven’t really messed with any of the configs, yet after adding a couple of components the build times are getting incredibly long(around 40 sec is no exception), that is on the first run of npm run server, after a while(few changes in files, watch triggered couple of times), it will get stuck on 90% optimize assets and then crash with the error below.

I’m really not sure how to debug this, and I’m not aware of doing something hacky in my code(there are no typescript errors at very least, and I’m not aware of any cycle dependency either) that could possibly cause it to go mental like this.

How should I proceed? Are there any common mistakes that would cause this, and I should look for? Would it help if I posted my repo? 😐

I’m running the latest version of angular2-webpack-starter and node 5.7.0

 90% optimize assets
<--- Last few GCs --->

  282958 ms: Mark-sweep 1378.9 (1456.7) -> 1381.9 (1456.7) MB, 2960.5 / 0 ms [allocation failure] [GC in old space requested].
  285856 ms: Mark-sweep 1381.9 (1456.7) -> 1381.9 (1456.7) MB, 2898.3 / 0 ms [allocation failure] [GC in old space requested].
  288814 ms: Mark-sweep 1381.9 (1456.7) -> 1377.1 (1456.7) MB, 2957.6 / 0 ms [last resort gc].
  291789 ms: Mark-sweep 1377.1 (1456.7) -> 1378.6 (1456.7) MB, 2975.3 / 0 ms [last resort gc].


<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0xff19f0e3ac1 <JS Object>
    1: copyMap [/srv/bubble/users/ar/ng2-base/repo/node_modules/typescript/lib/typescript.js:1198] [pc=0x3b78ca2abb95] (this=0x36735faa3a1 <an Object with map 0x1c3192bf1da1>,source=0x1a165d296929 <an Object with map 0x1c3192bbc3a1>,target=0x9118a8a3ef1 <an Object with map 0x2b40e4710441>)
    2: objectTypeRelatedTo(aka objectTypeRelatedTo) [/srv/bubble/users/ar/ng2-base/repo/node_modules/typesc...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory
Aborted