"uninitialized constant Sass::Script" after upgrade 4.0.5 -> 5.0.1

Question

"uninitialized constant Sass::Script" after upgrade 4.0.5 -> 5.0.1

rvrm opened this issue 9 years ago · comments

(..)/gems/ruby-2.1.2/gems/sass-rails-5.0.1/lib/sass/rails/helpers.rb:11:in `<top (required)>': uninitialized constant Sass::Script (NameError)

Running Rails 4.2.0. Happened to anyone else yet?

Rafael Mendonça França · Answer 1 · Fri Feb 27 2015 01:34:06 GMT+0800 (China Standard Time)

This constant is defined by sass gem. If you are getting this error the gem is not being loaded. As we require 'sprocekts/sass_functions' and it require sass I don't see how this is a problem on this gem.

Let us know if you can reproduce the error in an empty application.

Timo Sulg · Answer 2 · Wed Mar 04 2015 01:30:36 GMT+0800 (China Standard Time)

I encountered same issue after changing version number 4.0.5 to 5.0.1, moved back because i found no fix for that issue.

REVORM · Answer 3 · Wed Mar 04 2015 02:12:43 GMT+0800 (China Standard Time)

I was able to track down two gems which seemingly caused problems in my setup:
"Haml" and "Coffee-Filter"

The "haml" gem I upgraded to version 4.0.6. The "Coffee-Filter" gem I could remove from the gemfile (no longer needed).

For testing purposes I reinstalled the latter again to verify: The "uninitialized constant" error message then appeared again.

Obviously this is no final evidence, just posting it here to maybe help you with your setup.

Nick Zadrozny · Answer 4 · Mon Mar 30 2015 02:11:18 GMT+0800 (China Standard Time)

For posterity: I saw this briefly while experimenting with the Sprockets 3 beta today. Turns out I needed the sass gem to be explicitly required before sass-rails and sprockets. Easy enough!

Julio Protzek · Answer 5 · Mon Apr 13 2015 21:57:10 GMT+0800 (China Standard Time)

Thanks for the tip @nz! 🍻

Adam Gross · Answer 6 · Tue Apr 21 2015 01:57:29 GMT+0800 (China Standard Time)

Thanks @nz!

AwkDev · Answer 7 · Sun Apr 26 2015 13:11:22 GMT+0800 (China Standard Time)

Thanks @nz!

Jared Fine · Answer 8 · Thu Jun 18 2015 10:46:25 GMT+0800 (China Standard Time)

bundle update sass-rails did the trick for me when upgrading to Rails 4.2.2.

Jake Quain · Answer 9 · Sat Jun 20 2015 05:22:25 GMT+0800 (China Standard Time)

Thanks @jfine . Ran into this issue after upgrading from Rails 4.2.2 and that fixed it for me

Jared Fine · Answer 10 · Sat Jun 20 2015 05:34:27 GMT+0800 (China Standard Time)

Glad to help @quainjn

Brent Beer · Answer 11 · Fri Jun 26 2015 14:19:09 GMT+0800 (China Standard Time)

@nz for president. Thanks for the fix =)

Niall Duggan · Answer 12 · Tue Jan 26 2016 17:30:10 GMT+0800 (China Standard Time)

Thanks @jfine, just ran into the same issue and your suggestion helped me!

x-yuri · Answer 13 · Sat Jan 11 2020 06:39:58 GMT+0800 (China Standard Time)

Observed with sprockets >= 3, sass-rails < 5.0.2. sprockets once required sass. That allowed sass-rails to get away with not requiring it. Fixed in sass-rails-5.0.2. So either not update sprockets, or update sass-rails.