title: How to set up a debugger for a Chrome (or Edge) extension to properly breakpoint source files served outside of wwwroot?
body: <p>My project is laid out as so:</p>
  
  <pre><code>${workspaceFolder}
    /wwwroot
    /res
  </code></pre>
  
  <p>The /res directory is for serving files through a secure controller.</p>
  
  <p>My issue is when it comes to source debugging in VS Code via the "Debugger for Chrome" (or Edge) extensions.  </p>
  
  <p>If I put a breakpoint in a JS file in VS Code, it will work properly if the file exists under the wwwroot directory (it stops at that point in the source).  </p>
  
  <p>But if the js file is served from the /res directory (to /res in the web browser), VS Code will open up a new instance of that file, rather than the source instance.</p>
  
  <p>I think I need to do some kind of directory mapping for the debugger to translate <a href="http://localhost/res" rel="nofollow noreferrer">http://localhost/res</a> to ${workspaceFolder}/res for debugging the source files, but am unsure of the proper setup (possibly needing to set sourceMapPathOverrides, but my attempts have failed.).</p>