title: Chrome sources not showing a file that was generated from Typescript and has a source map
body: <p>I have a file that is dynamically loaded by sapui5 as a controller. I have altered my code so that I can leverage Typescript for Intellisense and fault detection.</p>
  
  <p>My JS file is successfully created, and runs correctly in Chrome. The DevTools/Sources/Network window does not list my 'FinalAssembly.controller.js' file, nor does it list the similarly named 'FinalAssembly.controller.ts' file.</p>
  
  <p>I have found that if I remove the '//# sourceMapURL=' line from the bottom of my file, Chrome will eventually list my JS file.</p>
  
  <p>I had read that use of the '//# sourceURL=' line at the top of my file would cause my file to be listed, but it wasn't, further, I read that use of this directive should allow me to vary the name that is displayed in the Sources list, it doesn't. It appears that Chrome is ignoring this directive.</p>
  
  <p>As of today, Chrome indicates that it is up to date at version 66. I have read lots of articles and Github issues over the last 4 hours that indicate that Source Maps tend to be problematic and can fail in some versions of Chrome.</p>
  
  <p>The map file itself works in Internet Explorer, but I can't really see myself developing with that.</p>
  
  <p>Has anybody debugged JS with a Source Map in Chrome 66? Can anybody suggest how I can debug my map file usage in Chrome?</p>
  
  <p>I have placed a very simple test created via VSCode (tsc.exe) at my website: <a href="http://www.ia.uk.com/TypescriptTest/default.htm" rel="nofollow noreferrer">http://www.ia.uk.com/TypescriptTest/default.htm</a> - on my Chrome 66 this one doesn't seem to download the map file at all (Fiddler didn't see any request for that). Doesn't show any TS view of the code. This is not a dynamically loaded library as per my original problem, but does show that there is a problem.</p>