Hi, I have an old bug from sprockets-rails rearing it's head on a project I work on now that uses the turbo-sprockets-rails3 gem. We're on turbo-sprockets-rails3 v. 0.3.6, and Rails 3.2.12. The symptoms and steps to reproduce are exactly those in the linked issue below. Let me emphasize that this one is a showstopper for us.
Hi, I have an old bug from sprockets-rails rearing it's head on a project I work on now that uses the turbo-sprockets-rails3 gem. We're on turbo-sprockets-rails3 v. 0.3.6, and Rails 3.2.12. The symptoms and steps to reproduce are exactly those in the linked issue below. Let me emphasize that this one is a showstopper for us.
https://github.com/rails/rails/issues/6803