title: DevTools failed to parse SourceMap
body: <p>I am trying to get my Webpack project to have a source map file.</p>
  
  <p>I finally got the settings right so that it would do that, but now I am getting this error: </p>
  
  <blockquote>
    <p>DevTools failed to parse SourceMap: <a href="http://MyServer/MyApp/bundle.js.map" rel="noreferrer">http://MyServer/MyApp/bundle.js.map</a></p>
  </blockquote>
  
  <p>I go to the URL it states and I find a json file with these properties:</p>
  
  <ul>
  <li><em>version</em>  - Set to 3</li>
  <li><em>sources</em>  - very long array of strings that seem to be webpack paths to my files.</li>
  <li><em>names</em>    - very long array of strings that seem to be random variables and functions.</li>
  <li><em>mappings</em> - very long string of seemingly random capitol letters and commas.</li>
  <li><em>file</em>     - set to bundle.js</li>
  <li><em>sourcesContent</em>  - Very Very long array of strings (over 10 million chars). All my source code.</li>
  <li><em>sourceRoot</em> - set to empty string</li>
  </ul>
  
  <p>It all seems to be valid json.  Unfortunally Chrome gives no reason why it failed to parse the source map.</p>
  
  <p><strong>Is there a way to get Chrome to say why it failed parsing the source map?</strong></p>
  
  <p><strong>Or, failing that, does anyone know why my source map would fail?</strong>  (My code is way too large to post, but here are my <a href="https://gist.github.com/Vaccano/eec28a554ddaaab3f631d15d8d05e988#file-webpack-config-js" rel="noreferrer">webpack.config.js</a> and my <a href="https://gist.github.com/Vaccano/eec28a554ddaaab3f631d15d8d05e988#file-package-json" rel="noreferrer">package.json</a> files.)</p>
  
  <p>NOTES: </p>
  
  <ul>
  <li>I have tried this with webpack 2.2.1, webpack 2.3.2 and webpack 2.6.1.</li>
  <li>Source maps work fine in IE 11 and Firefox.</li>
  <li>If I inline my source maps, then they work fine in Chrome DevTools, but then my bundle.js goes from 3 MB (already too big) to 16 MB (WAY too big).</li>
  <li>I have set "Enable JavaScript Source Maps" in settings (and the CSS one too).</li>
  <li>I tried using Chrome Canary, but it had the same issue.</li>
  <li>I am hosting in IIS.</li>
  </ul>