Unreadable: susy #21

Closed
ijy opened this Issue Dec 8, 2011 · 9 comments

7 participants

@ijy
ijy commented Dec 8, 2011

I've installed the compass-susy-plugin gem successfully and included it in my config.rb file (require 'susy') but when I import susy into my base stylesheet I get the following error:

error sass/screen.scss (Line 9: File to import not found or unreadable: susy.

If I then try including the container mixin it says it's undefined—as it's not loading susy.

@ijy
ijy commented Dec 8, 2011

It's also not in the load paths. The full error output is:

error sass/screen.scss (Line 16: File to import not found or
unreadable: susy.
Load paths:
/Users/ian/path/to/project/assets/stylesheets/sass
/Users/ian/.rvm/gems/ruby-1.9.3-p0/gems/compass-0.11.5/frameworks/
blueprint/stylesheets
/Users/ian/.rvm/gems/ruby-1.9.3-p0/gems/compass-0.11.5/frameworks/
compass/stylesheets
Compass::SpriteImporter)

@ijy
ijy commented Dec 9, 2011

On further testing this seems to be more a problem with the location of the config.rb file when using a non-standard Compass directory structure. I was using the following directory structure:

project/
config.rb
assets/
stylesheets/
css/
sass/

which resulted in the error. Moving the config.rb file to the stylesheets directory seems to resolve this issue however:

project/
assets/
stylesheets/
config.rb
css/
sass/

Is this intended behaviour? I could find no mention of this in any of the Compass/Susy docs.

@florianeckerstorfer

I have the same problem and I also modified the default compass directory structure.

images
js
sass
sass/style.sass
style.css

Note, that the CSS is in the project root directory. But it did also not work when I move the CSS into a css or stylesheets directory. Interestingly the CSS can be compiled on the initial compass create command. Only compile and watch do not work.

I've put the output of compass create, compass compile and compass frameworks in a Gist: https://gist.github.com/81c79904af7bb8e80070

@mirisuzanne
OddBird member

I've heard of this before, but the solution has always been on the config/ruby end which I know very little about. The best place to ask is on the compass google group. Sorry I was awol for so long, hope it's been sorted out.

@premasagar

I also had this and found that I didn't need to reorder the file structure. Instead of compiling and watching with sass --watch sass/style.scss:style.css from the project folder, I just used compass watch, and that worked.

In advance of this, the project was set up with compass create . -r susy -u susy

@vedovato

Dude, thank you very much! This "fix" should be posted somewhere. But, what cause this error?

@thanyawzinmin

I am also facing the same problem when using as a framework of "compass".
I do the installing susy as a gem. Still having this error .. till this night.

@HugoGiraudel

@DeivisonMaster You will have to speak English here. :)

@mirisuzanne
OddBird member

@DeivisonMaster best I can translate that, you're having trouble loading Susy in a Ruby environment? I think -r susy might be from Compass, and not something Sass does internally? But I am not an expert on Sass load paths or ruby rems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment