Closed gregors closed 9 years ago
I'm also getting that with rails 4.2.1.
Is this possibly due to recent sprockets releases? If you try downgrading sprockets-rails in your gemfile, does that fix it? (thinking of this b/c of #159)
@searls I'm using the sprockets gem that is included via my other gems. Do you have a version that is known to work?
Try specifying 'sprockets' at '2.12.3' in your Gemfile and see if that fixes it. Wouldn't be surprised if you're pulling in sprockets 3+ and that's what triggered the break.
On Thu, May 28, 2015 at 9:44 AM, Daniel Searles notifications@github.com wrote:
@searls I'm using the sprockets gem that is included via my other gems. Do you have a version that is known to work?
Reply to this email directly or view it on GitHub: https://github.com/searls/jasmine-rails/issues/163#issuecomment-106316097
I'll try that. It is currently locked at 2.3.1.
I was wrong, sprockets-rails
is locked at 2.3.1. sprockets
is locked at 3.1.0. I'll try going backwards.
It was all user error on my part. It all works if I make sure to set RAILS_ENV=test
Seeing this blow up when run with rails 4.2.1