Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
Brad Bucceri
7,102 PointsSass has stopped working - Terminal error
Hi All,
I would really appreciate some assistance if possible. I think I may have updated something and now compass/sass/susy seems to not be working.
The error I get when i navigate to my site folder and tell compass to watch is this:
```Gem::LoadError on line ["1638"] of /usr/local/rvm/rubies/ruby-1.9.3-p392/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb: Unable to activate susy-2.1.1, because sass-3.2.18 conflicts with sass (~> 3.3.0)
I guess it's some kind of conflict but I'm new to using this stuff.
Thanks in advance :)
Brad
2 Answers
Brad Bucceri
7,102 PointsI seem to have fixed it. I uninstalled the new susy gem (2.1.1 i think) that i updated yesterday and then installed version 1.0.9. I think this was causing the issue as compass will now watch for changes. I'm not sure I understand why it did this so if anyone can shed some light I would be grateful :)
Best,
Brad
James Barnett
39,199 PointsSusy 2.x requires Sass 3.3 whereas the current version of Compass doesn't support Sass 3.3.
To work around this conflict use the pre-released version of Compass, install it with
gem install compass --pre
Brad Bucceri
7,102 PointsThanks James, I'll give this a try later on! :)
Brad