Chrome and SASS source maps

I must say this is single most valuable answer here I have ever seen: precise, quality and concise!

bundler is pretty smart so it is just sufficient to demand 'compass', '~>1.0.0.rc.0' and bundle update will do the rest with dependencies.

However, and this is a major thing, that is not enough without changes to config.rb, themename.styles.scss and themename.normalize.scss

I can confirm that it even works with guard and live reload although I've read a ton of posts that said it cannot be resolved. I prefer drush guard to simple compass watch or even more to bundle exec compass compile which I never (needed) to use.

There are some caveats: you must take care not to mix units as SASS 3.3 is more strict than 3.2 and there are some other changes and deprecations you should learn about. So you may end up with error sass/theme.styles.scss (Line xxx of sass/......scss: Incompatible units: 'px' and 'rem'.) which you have to trace and change. The simple explanation is that you cannot add pixels to ems and somewhere rem as a unit does not work (some functions do not support it like add-grid()). On a relatively complex site I needed about an hour to fix those errors and compile successfully.

I see no reason not to include this patch with next Omega release (if there is going to be one at all :( )

I can confirm that it is OK. I made a new Drupal installation, pulled omega-4.x-dev, created omega-new subtheme using drush owiz and then executed bundle install

mladen:~/Sites/omega/sites/all/themes/omega_new 16:04:31 $ bundle install
Fetching gem metadata from https://rubygems.org/..........
Fetching additional metadata from https://rubygems.org/..
Resolving dependencies...
Using addressable 2.3.6
Installing sass 3.4.1
Installing sassy-maps 0.4.0
Installing breakpoint 2.5.0
Installing timers 1.1.0
Installing celluloid 0.15.2
Using chunky_png 1.3.1
Using coderay 1.1.0
Installing multi_json 1.10.1
Installing compass-core 1.0.1
Installing compass-import-once 1.0.5
Using rb-fsevent 0.9.4
Using ffi 1.9.3
Installing rb-inotify 0.9.5
Installing compass 1.0.1
Using compass-normalize 1.5
Using compass-rgbapng 0.2.1
Using compass-validator 3.0.1
Using css_parser 1.3.5
Using eventmachine 1.0.3
Using http_parser.rb 0.6.0
Using em-websocket 0.5.1
Installing formatador 0.2.5
Installing listen 2.7.9
Installing lumberjack 1.0.9
Using method_source 0.8.2
Installing slop 3.6.0
Installing pry 0.10.1
Using thor 0.19.1
Using guard 2.6.1
Using guard-compass 1.1.0
Installing guard-livereload 2.3.0
Using guard-shell 0.6.1
Using oily_png 1.1.1
Using rb-fchange 0.0.6
Installing sass-globbing 1.1.1
Installing singularitygs 1.3.0
Installing susy 2.1.3
Installing toolkit 2.6.0
Installing yajl-ruby 1.2.1
Using bundler 1.6.2
Your bundle is complete!
Use `bundle show [gemname]` to see where a bundled gem is installed.
Post-install message from compass:
    Compass is charityware. If you love it, please donate on our behalf at http://umdf.org/compass Thanks!

After fetching all needed gems and dependencies, compass compile produced source maps as expected:

mladen:~/Sites/omega/sites/all/themes/omega_new 16:10:24 $ compass compile
    write css/omega-new.no-query.css
    write css/omega-new.no-query.css.map
    write css/omega-new.normalize.css
    write css/omega-new.normalize.css.map
    write css/omega-new.styles.css
    write css/omega-new.styles.css.map
mladen:~/Sites/omega/sites/all/themes/omega_new 16:16:26 $ 

I included whole bundler listing where you can see what is pulled new and what was used from previous omega setup (though this may not be exact due to some of my previous testing).

@Fubhy, it would be nice to have just Gemfile and not any version declared, however, I am not sure that it will still be working some time from now. These gems are changing like crazy and at some point people may get p*ssed as dependencies may be more broke that they would work. Until recently, it was nearly impossible to get source maps and work with omega (I tried that myself in May 2014 and failed) and kept trying until jwilson3 resolved change in config.rb which enabled the whole thing.

I hope that this combination would continue to work but we will have to constantly monitor not to have some dependency broken.

As it is now, with this exact version of gems, everything works.

...therefore, it would make sense to declare some versions in Gemfile that are tested and proved to work and to make progress in each release toward newer versions of gems.

New Omega release may be justified even for some gems change or smaller improvements, as we learn from all modern projects, the world seems to abandon great releases and focus on smaller but more rapid improvements (even WP does that).

Personally, I do not like this rapidness, I prefer solid and tested releases and do not like the need to update every week for some small thing I will never experience but then, when I face a problem I do get "itchy" why something is not fixed when it known for some time.

There I said it and I add that I am comfortable with Fubhy release pace although I am not too comfortable that project is still here after that ugly dispute with Jake, but that is another issue.

...and we can do new releases every now and then with the latest Gem versions.

I'd add to that: ...latest Gem versions that are tested and proved to work (although it may seem self evident but that is precisely why fubhy asked if those work because sometimes our special cases may not be the case for everyone and sometimes, yes, we are just too tired and cannot see the forest for the trees anymore.

This issue is overcome by new Omega version 4.4 and by moving to node based workflow (that raises new set of issues) I think we can assume this fixed.