title: Sourcemaps only working when clicking link from Chrome console's console.log
body: <p>I'm generating inline sourcemaps for my JS using Gulp and <a href="https://www.npmjs.com/package/gulp-sourcemaps" rel="nofollow noreferrer">gulp-sourcemaps</a> and uglifying with <a href="https://www.npmjs.com/package/gulp-uglify" rel="nofollow noreferrer">gulp-uglify</a>. </p>
  
  <p>In the Chrome developer tools, when I visit the <em>sources</em> tab directly and click on my uglified/sourcemapped file, Chrome doesn't try to parse the sourcemap and just displays the uglified file.</p>
  
  <p>However, when the console displays a message (such as from <code>console.log</code> or an exception) with a link to the file and line number (e.g. <code>app.js:81</code>), I can click on it and am taken to the <em>sources</em> tab of the dev tools, and the sourcemap is correctly parsed and the original file is shown. </p>
  
  <p>Here's two screenshots where you can see the same file, one with the sourcemap parsed and one with it unparsed:</p>
  
  <p><img src="https://i.stack.imgur.com/tY4ca.png" alt="parsed">
  <img src="https://i.stack.imgur.com/041dG.png" alt="unparsed"></p>
  
  <p>Am I doing something wrong here, or misunderstanding how sourcemaps are supposed to work? I want to be able to visit the <em>sources</em> tab directly and see the original file, not the uglified one. </p>
  
  <p>Let me know if you need any more info.</p>