<p dir="auto"><strong>Do you want to request a <em>feature</em> or report a <em>bug</em>?</strong></p>
<p dir="auto">Bug</p>
<p dir="auto"><strong>What is the current behavior?</strong></p>
<p dir="auto">When using AggressiveSplittingPlugin, 2 problems.  Firstly it doesn't work unless you also include "CommonsChunkPlugin", as this then has the bootstrap code, (webpackJsonp etc).  Also if not using "CommonsChunkPlugin" duplicates are created.  eg. If say I used PouchDB twice in 2 entry points I get 2 350k files,..</p>
<p dir="auto">But the biggest problem, if you have more than 1 entry point using Watch mode, first compile is fine, successive compiles give errors like -&gt;</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="ERROR in chunk 1 [entry]
8a7cd0cd2cc5f21ec12a.js
Conflict: Multiple assets emit to the same filename 8a7cd0cd2cc5f21ec12a.js

ERROR in chunk 3 [initial]
93a8d32df50e5f918ebe.js
Conflict: Multiple assets emit to the same filename 93a8d32df50e5f918ebe.js
etc.
"><pre class="notranslate"><code class="notranslate">ERROR in chunk 1 [entry]
8a7cd0cd2cc5f21ec12a.js
Conflict: Multiple assets emit to the same filename 8a7cd0cd2cc5f21ec12a.js

ERROR in chunk 3 [initial]
93a8d32df50e5f918ebe.js
Conflict: Multiple assets emit to the same filename 93a8d32df50e5f918ebe.js
etc.

</code></pre></div>
<p dir="auto">Also worth noting, on these successive compiles, it again then duplicates files, eg.  It shows 2 350k files again, like when not using "CommonsChunkPlugin".</p>
<p dir="auto">A temporary solution while developing in watch mode only have 1 entry point, and only work on this.  Once you are happy re-include all entry points and do a full compile again.</p>
<p dir="auto"><strong>If the current behavior is a bug, please provide the steps to reproduce.</strong></p>
<p dir="auto">Create a project with 2 entry points, start compile in watch mode.<br>
Now modify a file to cause a recompile.</p>
<p dir="auto"><strong>What is the expected behavior?</strong></p>
<p dir="auto">It works like the first compile, and doesn't error.</p>
<p dir="auto">been battling with this error for a day now, really putting me off trying to upgrade to webpack 2 :)</p>
<p dir="auto">webpack 1.x runs without any issue. webpack 2.x runs, but only if i don't use any loaders</p>
<p dir="auto">As soon as a loader is added, i get the <code class="notranslate">Segmentation Fault: 11</code> error.</p>
<p dir="auto">tried deleting &amp; reinstalling node_modules.<br>
tried reinstalling node (running node 4.2.2, npm v2.15.0).<br>
tried deleting &amp; reinstalling global node_modules<br>
tried reinstalling global webpack modules<br>
tried forcing version of fsevents (from <a href="https://github.com/sass/node-sass/issues/1107" data-hovercard-type="issue" data-hovercard-url="/sass/node-sass/issues/1107/hovercard">this post</a>). Cannot complete install.</p>
<p dir="auto">the loaders i am trying to get running are for typescript (tried both ts-loader and awesome-typescript-loader)</p>
<p dir="auto">I see typescript compilation has been working in the past from <a href="http://www.jbrantly.com/es6-modules-with-typescript-and-webpack/" rel="nofollow">this blog post</a>, so i know it at least works for someone</p>
<p dir="auto">should webpack 2.x be able to run with node 4.4.x without this error? Anyone else have it working with typescript?</p>
<p dir="auto">running OSX 10.11.1</p>