-
-
Notifications
You must be signed in to change notification settings - Fork 879
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatible with sass 3.2? #111
Comments
Hey Fabian, you saved me a lot of time here, thanks for reporting this. Out of curiosity, how did you find out the exact spot where your sass code breaks, because I only see a very general debug message? I use # Gemfile
gem 'sass', '3.2.0.alpha244' Thomas |
Well, I knew which file was causing the error, so I started commenting out parts until I could track it down to bourbon. Just plain old trial and error. |
I was unable to reproduce on a new Do you experience the error when using any other bourbon mixins? Is it isolated to just Are you using any other gems that compile scss? Like compass or bootstrap-rails? |
Sorry, this has nothing to do with If you still want to reproduce, it only happens when you use Best regards, |
Same setup here, so that only sass releases before the final 3.2.0 seem to be working with pow. Thanks for referencing the sass issue report. |
A little more info, if anyone is still wondering when we can update (I still am): |
Hi,
I just updated rails in an application to 3.2.8, and in the process sass was updated to version 3.2.0. With the update I received the not very explanatory message 'EOFError - end of file reached' when accessing any page which compiles SCSS-files.
I tracked the problems down to bourbon-mixins, but I'm not sure how to fix them. The sass-changelog mentions some incompatibilities (http://sass-lang.com/docs/yardoc/file.SASS_CHANGELOG.html), but after a very quick look over the source I didn't find them applicable to the mixins I was using (in this case
border-radius
).I'm using using
bourbon (2.1.1)
. I was able to temporarily fix the problem by adding the following to myGemfile
:If you need any more information I will provide it happily. Thank you!
Fabian
The text was updated successfully, but these errors were encountered: