Unable to activate susy-2.1.1, because sass-3.2.17 conflicts with sass (~> 3.3.0)

两盒软妹~` 提交于 2019-11-30 09:57:26

If you use Bundler, it will ensure that the gems in your Gemfile are the ones used by your project. So your Gemfile should specify "susy", "~>2.1.1" and "sass", "~>3.3.2", plus any other that you require, such as "breakpoint", "~>2.4.1". It then won't matter what versions are installed inside your Ruby gems folder. When you then do a 'bundle install', Bundler ensures that your project will only use the correct dependencies. This is, of course, a CLI instruction through the terminal. Alternatively, simply do a 'sudo gem uninstall sass -v 3.2.17', if you don't want to use Bundler.

gem install compass --pre

if you ended up uninstalling the sass 3.3.0 gem you should reinstall that first.

Simon Gamble

The best way without a doubt is to install Susy via the Compass Susy Plugin. This will avoid conflicts with other Compass projects that require the current version.

Commands:

gem install compass
gem install compass-susy-plugin

I'm using Ubuntu server 14.04 and I had the same problem and this is what I have done

  • Remove all my gems with gem uninstall gemname
  • Install bundler with sudo apt-get install bundler
  • Create a Gemfile as @Remy said before. Here is a Getting Started With Bundler Guide
  • And finally bundle install

After that, bundler create a Gemfile.lock where are specified all the needed gems and its versions, so you can use it safely.

https://teamtreehouse.com/forum/cant-make-susy-211-working

User: Iago Wandalsen Prates

gem uninstall compass

gem uninstall sass

gem uninstall susy

gem install susy

gem install compass --pre

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!