Require Sass::Deprecation module

[beagleknight]

Hi there!

I was developing a rails application using the sassc-rails gem and I got an error like this:

NameError: uninitialized constant Sass::Deprecation

Then I realized that this gem was including the latest version of sass and it is requiring the modules individually in the lib/sassc/script.rb file.

I am not sure if this fix belongs here or the require is missing in some sass file.

Thoughts?

[deivid-rodriguez]

Yeah, the alternative would be sass requiring sass/deprecation every time it's used. That seems more explicit to me.

[meowsus]

@deivid-rodriguez I believe I did that same alternative in #70

This resolves #69

[meowsus]

@beagleknight for reference sass/sass#2338

[deivid-rodriguez]

sass has rejected the alternative patch, so the fix needs to happen here.

Given that sass does not support current usage, maybe it's better to require the whole of sass to avoid future breakage.

[meowsus]

@deivid-rodriguez that would be more futureproof, for sure, but I'm curious what the negative effects of this might be.

@bolandrm is there a reason why we're picking and choosing sass functionality and not requiring the whole library?

[meowsus]

@bolandrm I don't mean to be a bother, but I was curious if you had an idea when of when we might expect a patch. This issue seems to be affecting a good number of folks and the entirety of our platform's integrators. Instead of having us patch manually, we were hoping for a fix from upstream.

Thanks, and sorry for the prodding.

[robinboening]

I also ran into this issue yesterday. Would be great to see this / a patch merged and a new release. Thanks folks!

[bolandrm]

Thanks all - please try out 1.11.4 and let me know if there are any issues.

[robinboening]

Thanks! I will try and report back.

[beagleknight]

Thank you! 😄

[meowsus]

Yes! Thank you! I can confirm that this took care of my error.

[robinboening]

I can also confirm it works with v1.11.4 now! Thanks a lot!