undefined method `environment' for nil:NilClass

[jcoyne]

sstephenson/sprockets#537

The error occurs when sprockets is upgraded from 2.11.0 to 2.11.1 using Rails 4.

@josh says:

This is a sass-rails issue. It monkey patches private Sprockets classes. The fix will need to be made there.

[josh]

/cc @rafaelfranca

[josh]

This is going to be tricky to get working on sass 3.3. I think sass-rails will have to pin to 3.2 for now and use the old Sprockets::SassImporter tracking technique.

[josh]

All of the glob stuff requires a dynamic reference to context which won't be possible if the importer reference needs to be marshable. A pretty annoying requirement by sass core. I'd probably guess they didn't realize this was the case but theres a ton of circular references that looped the importer into whatever instance is actually being cached.

[rafaelfranca]

Right! I really wish we could remove our SassImporter and use sprocket's one but it will be hard without deprecating the glob importing.

[jcoyne]

Since current version of sass-rails is incompatible with sprockets 2.11.1, wouldn't the expedient fix be to release a patch version locked to sprockets 2.11.0?

[josh]

Another approach for supporting globs would be to disable sass caching. That avoids all the marshaling problems. You'll still have sprockets caching to help keep things fast.

[rafaelfranca]

Yes. I'm doing this right now. But I'm more concerned about the future of this project. I don't want to lock sprockets forever.

[jcoyne]

Excellent. Thanks @rafaelfranca.

[jforberg]

I get this too, whenever I try to import files. This is on a new project running vanilla everything.

[waterlink]

Thank you @rafaelfranca
With sprockets locked to <= 2.11.0 it works for me.

[rafaelfranca]

4.0.2 released

[rafaelfranca]

I really don't know how this continue this gem if Sprockets::SassImporter is public and I can't use context to make glob work.

We also can't just deprecate it because sprockets alone doesn't work with Rails features.

[josh]

SassRails should define its own private SassImporter.

[josh]

I'm more stumped to how to make glob importers work in Sass >= 3.3.

[spohlenz]

@josh What issues are you seeing specific to Sass 3.3? I haven't noticed any difference in behaviour between 3.2 and 3.3.

[gracegimon]

While locking sprockets is working for Rails version 4.02. for Rails version 4.0.4 it isn't:

rails (= 4.0.4) ruby depends on
  sprockets (2.12.0)

[ivanreese]

@gracegimon locking sass-rails to 4.0.2 seem to work around this issue temporarily.

gem "sass-rails", "4.0.2"

Or if you prefer,

gem 'sass-rails', '~> 4.0.0', '>= 4.0.2'

[sharp]

do not work with Rails 4.0.4

Bundler could not find compatible versions for gem "sprockets":
  In Gemfile:
    sass-rails (= 4.0.2) ruby depends on
      sprockets (<= 2.11.0, ~> 2.8) ruby

    rails (= 4.0.4) ruby depends on
      sprockets (2.12.0)

[dogweather]

Similar problem with Rails 4.1.0.

[robin850]

@SharpV : You should rm Gemfile.lock and be sure to have sass-rails version 4.0.3. Then you can run bundle install without any problem normally.

[jinhianlee]

Thanks @robin850. I followed your instructions and bundle install works but I still get the original error _(undefined method environment' for nil:NilClass)_ when pre-compiling the asset pipeline on Heroku. Gem versions: ruby 2.1.1 sass 3.2.19(also tested withsass 3.3) sass-rails 4.0.3 rails 4.1.0` (ref: '968c581ea34b5236af14805e6a77913b1cb36238', branch: '4-1-stable')

Is there a 'known-good' combination of sass & sass-rails that works with Rail 4.1.0?

[dogweather]

Yep, through a lot of trial and error I found a working combination: https://gist.github.com/dogweather/11150333

That's simply my app's Gemfile and Gemfile.lock. Note that a bundle update still produces the error, but bundle install with these locked-in versions works.

[jinhianlee]

@dogweather Thanks, will give it a shot!

[MarkMurphy]

There seems to be a lot going on here can someone summarize the status of this issue, is anyone working it?

[rafaelfranca]

This specific issue is already fixed. Make sure you use sass-rails 4.0.3.

[dogweather]

I'm sorry, I don't understand. It seems like, if we're using Rails 4.1, then we need to remember to lock sass-rails to 4.0.3. Otherwise, the dependencies can't be resolved. Is this right?

And so it seems like the issue isn't fixed: Sass-rails depends on an older version of sprockets while Rails depends on a newer version. Is this accurate? Is there a GitHub issue or branch where this is being worked on?

[rafaelfranca]

No, it is not correct. In fact Rails 4.1.0 generates the Gemfile already using sass-rails 4.0.3. Also rails doesn't define a newer version of sprockets.

One thing that is correct is that we are depending on an older version of sprockets and we need to remove that. But this doesn't mean that sass-rails or rails is broken. It just means you have to be sure you are using the right version.

In the next weeks I hope I can remove this dependency freeze and release sass-rails 4.0.4.

[jkbailey]

+1 for fixing this

[msokk]

+1

[reconstructions]

Is anyone fixing this?

[rafaelfranca]

It is already fixed in the latest version