According to this issue https://github.com/rails/sass-rails/pull/192 sass-rails hasn't support for Sass 3.3 yet.
But it seems that sass-rails-source-maps has been depending on Sass 3.3 since the very beginning. So is there a way to use this gem with sass-rails?
According to the readme with sass-rails-source-maps, Chrome dropped support of the Source Maps files from Sass older than version 3.3.
Does that mean there is no way of using Sass Source Maps with Chrome devtools now?
There is a great new drop in replacement for sass-rails, which is not only faster, but also has the option to use inline source-maps.
Just add it to your Gemfile
#gem 'sass-rails', '~> 5.0' gem 'sassc-rails' and add the configuration
# config/environments/development.rb config.sass.inline_source_maps = true Don't forget to restart your server, then you should see it working in the inspector:
You can find the repo here: https://github.com/sass/sassc-rails
I was able to use source maps with Rails 4.1 in this way:
by using the beta of the sass-rails gem (5.0.0.beta1), which isn't always the safest thing to do, and by
adding the "compass-rails" ("2.0.1") and the "compass-rails-source-maps" ("0.0.8") gems. I don't use Compass in this particular project, but the compass-rails-source-maps gem needs the compass-rails gem (obviously), and it worked great for me.
I didn't have much luck with the sass-rails-source-maps gem, but I didn't spend a lot of time with it; perhaps it isn't compatible with the beta sass-rails gem, or something else I'm using.