Nikita Vasilyev

I believe it could be done by using a single rule, e.g.: ``` javascript { from: new RegExp('^http://localhost/(otherpartof/samepath/)?'), to: 'src/some.Web' } ```

> And if the paths are not next to each other, do you allow for regex tag replacement? Capture groups work, e.g.: ``` javascript { from: new RegExp('^http://localhost/(somesection)/otherpart/of/samepath'), to: 'src/somepath/$1'...

How often do you need to turn Autosave off and why?

I don’t like my Chrome toolbar being bloated. I’m not going to add a toolbar icon that the only purpose is to toggle the extension on/off. You can do the...

I’m glad you like it but isn’t it easier to open chrome://extensions/ and disable DevTools Autosave rather than opening chrome://extensions/, clicking Options, and unplugging a pipe?

Not really following. Autosave treats all URLs as absolute. Just put `^http://domain.com/` into the match field?..

I guess that would be really hard to do. I have to dig how [FireSASS](https://github.com/nex3/firesass) work.

Locating SCSS files probably the easiest thing here. There is a [sourceURL for JavaScript](http://blog.getfirebug.com/2009/08/11/give-your-eval-a-name-with-sourceurl/). We could use something like this for CSS. [Mozilla and Google work on Source Mappings format](http://www.infoq.com/news/2011/08/debug-languages-on-javascript-vm)....

I [dug FireSASS](https://github.com/nex3/firesass/issues/7#issuecomment-3545103). It won’t help here. How FireSASS work? Here is an example. index.sass: ``` sass $blue: #3bbfce body background-color: $blue ``` ``` $ sass --debug-info index.sass:index.css ``` index.css...

I accidentally discovered, that [applying patches](https://github.com/NV/chrome-devtools-autosave/issues/13) to SCSS, Less and Stylus works well on simple cases :)