Nikita Vasilyev

No, I’m afraid. [Source Maps](http://www.html5rocks.com/en/tutorials/developertools/sourcemaps/) does not allow to edit transformed file. To make it work, we have to connect SASS/Less/Stylus compiler to DevTools so it would recompile SASS/Less/Stylus file...

Looks like [chrome.storage](http://code.google.com/chrome/extensions/storage.html) just went out of an experimental namespace. I’ll give it a try.

How much do you have, by the way?

Still looking for help. - [Make Asset Pipeline work with Chrome DevTools Autosave](http://stackoverflow.com/questions/9731907/make-asset-pipeline-work-with-chrome-devtools-autosave) - http://www.ruby-forum.com/topic/3861633

@trenkwill Create a routes.js file: ``` javascript exports.routes = [ { from: new RegExp('http://my-rails-app.local/assets/(.+?\.css)'), to: '/Users/nv/my-rails-app/app/assets/stylesheets/$1' }, { from: new RegExp('http://my-rails-app.local/assets/(.+?\.js)'), to: '/Users/nv/my-rails-app/app/assets/javascripts/$1' } ] ``` and run `autosave --config...

@cemerson could you put the whole log here?

Hm, it works for me. `sudo npm run-script -g autosave autostart` on Mac OS X runs https://github.com/NV/chrome-devtools-autosave-server/blob/master/scripts/autostart.sh#L4. As a workaround you can manually put [com.chrome.devtools.autosave.launchd.plist](https://github.com/NV/chrome-devtools-autosave-server/blob/master/scripts/com.chrome.devtools.autosave.launchd.plist) into $HOME/Library/LaunchAgents/ and do `launchctl...

Just made it work on Ubuntu, although I haven’t tested it much since I’m not Ubuntu user. Please `npm link` the repo and let me know how it goes.

I don’t know. It might be a good idea to ask this question on [npm mailing list](https://groups.google.com/forum/?fromgroups#!forum/npm-).

3 of 4 @media tests are passed. Fails on crazy case: `@mediaall {}`.