DevTools failed to link network resource to filesystem.

Platform: Mac10.12.6 (16G29) with localhost running through Vagrant.
Chrome version: Version 63.0.3239.108 (Official Build) (64-bit)


What are the details of your project?
- Source code (if any): private repo
- Build System: webpack
- HTTP server: webpack-dev-server

Assets failed to link (or incorrectly linked):

There is no longer any option to manually network sources to local files. This is an issue because of an issue when chaining webpack loaders 
(style-loader backup to css-loader/sass-loader used for HMR with webpack)
I am debugging the issues within this chain for a solution but the issue arises from the network source location being: 
/vagrant/XXXXX/static/scss/app.scss
and the local file location being
file://Users/XXXXXX..../static/scss/app.scss (this is linked within the workflows)

I'm sure there is an optimal setup (which I am looking into) with the loaders that results in the correct filename even through vagrant with HMR but removing the ability to manually map edge cases is a big issue for local development where edge cases do occur.

You used to have this feature and it is still in your documentation here:
https://developers.google.com/web/tools/setup/setup-workflow
this option: `Map to File System Resource`

The automatic mapping is great but we still need a way to do this manually.