title: Chrome Dev Tools - Mapping network resource to local file not working
body: <p>Is Local file mapping dev tools alternative to Charles proxy in firefox? I am trying to map a <strong>remote</strong> server resource to a local file, but it doesn't seem to be working. The console statements and changes in the JS file doesn't seem to be applied when I reload the page. </p>
  
  <p>I can see the local folder and file listed in the sources folder. Also, see that the sources doesn't show the original JS file. But I see this message in the sources tab for the local file.</p>
  
  <p><strong>Workspace mapping mismatch</strong></p>
  
  <p>Rest of the warning states that the file in local folder is different from the remote loaded file. Why is that a problem, wouldn't that be always the case, since you want to edit the file locally?</p>
  
  <p>What am I missing? Any pointers to fixing this? Is my assumption wrong that this feature in chrome dev tools can allow loading a resource locally, as if it was loaded from the original location?</p>
  
  <p>I tested this again with a simple html page with a single js file having a simple console log statement - "loading remote file ...". This file is mapped to a local js with a different log statement "loading local file.." However, I still see the log message from the remote file.</p>
  
  <p>Added snapshot from dev tools sources tab for more context. Sources tab shows the local folder and file correctly, but shows the mapping warning. Also notice that sources doesn't have the remote.js file anymore.
  <img src="https://i.stack.imgur.com/RgFbv.png" alt="Snapshot from dev tools sources tab"> </p>