uninitialized constant Sprockets::DigestUtils in 0.9.9

Question

uninitialized constant Sprockets::DigestUtils in 0.9.9

Opened this issue 9 years ago · 16 comments

Hi. I just upgraded to 0.9.9 and I'm getting this error during precompilation of assets:

uninitialized constant Sprockets::DigestUtils

This is because Sprockets::DigestUtils is only available in sprockets 3.0+, but due to version restrictions from another gem in my app, I can only use sprockets 2.x.

If requirejs-rails depends on a sprockets 3.x feature, then sprockets needs to be added as a dependency with >= 3.0.

Answer 1 · 2015-08-16T20:07:27.000Z

@monfresh Hmm, I thought this got fixed recently with Sprockets 2.x backwards compatibility.

Answer 2 · 2015-08-18T13:13:45.000Z

Stumbled on this too today, c7babb6 is the culprit.

@carsomyr What do you refer to by "Sprockets 2.x backwards compatibility"?

I think we would be compatible if we change the code as described here. What do you think?

Answer 3 · 2015-11-28T03:46:46.000Z

Any updates on this issue?

Answer 4 · 2015-11-28T03:50:09.000Z

@monfresh Could you check master?

Answer 5 · 2015-12-01T19:16:13.000Z

Also seeing this issue on 0.9.9 w/ sprockets 2.12.4. Same restriction @monfresh mentioned to being able to update sprockets.

Answer 6 · 2015-12-26T20:27:07.000Z

@carsomyr Was this supposed to be fixed in 1.0.0? I'm still seeing the same error uninitialized constant Sprockets::DigestUtils.

Answer 7 · 2015-12-27T04:03:06.000Z

@monfresh I am getting the same error. 1.0.0 was supposed to fix a precompilation error I was running into.

EDIT: So it seems that DigestUtils is only available in Rails 4. I am running into this error because my project is running Rails 3.2.22

Answer 8 · 2015-12-30T02:16:00.000Z

Ok so I found a workaround for this using Rails 3.2.22 (didnt try for any other versions) and requirejs-rails 1.0.0.

If you just copy and paste DigestUtils.rb file into config/initializers, it will attach DigestUtils into sprockets and work correctly.

NOTE: the main thing that I had to do to get it to work is change the default pack_hexdigest method from
bin.unpack('H*'.freeze).first
to
bin.hexdigest

Answer 9 · 2015-12-31T02:33:13.000Z

@passa763 Is there some problem with

bin.unpack('H*'.freeze).first

It seems to work for me.

Answer 10 · 2015-12-31T02:34:59.000Z

Can y'all test the commit above? @monfresh @passa763 @Chrisell

Answer 11 · 2015-12-31T04:16:26.000Z

@carsomyr bin needs to be a string in order for unpack to work. But for me, bin is a <Digest::MD5> object.

EDIT: what Rails version are you using?

Answer 12 · 2016-01-07T00:13:10.000Z

All, I'm working on a solution that everyone can use. Apparently there are some version inconsistencies to sort through as to which methods are and aren't available for use.

Answer 13 · 2016-04-21T19:15:14.000Z

I'm having this issue with rails 4.0.13 and requirejs-rails 1.0. I also tried requirejs master. Same problem.

Answer 14 · 2017-07-25T06:18:26.000Z

I'm using Rails 4.2.4 and requirejs-rails 1.0.0. Getting same error, please help!

Answer 15 · 2017-07-25T06:24:40.000Z

Does using master help?

Answer 16 · 2017-07-25T06:38:00.000Z

I commented both sprockets and sprockets-rails, but when I run the command,

gem list | grep sprocket

o/p is,
sprockets (3.7.1, 2.12.4)
sprockets-rails (3.2.0, 2.1.4)

After commenting gems, I'm now able to run assets:precompile.