This library is incompatible with browserify-rails, because dependency modifications do not invalidate the cache.
I'm able to get turbo-sprockets-rails3 to ignore browserify-rails by dropping this line in an initializer, but this has the drawback of removing all benefit from using turbo-sprockets-rails3.
It looks like this was encountered with Sass/Less in the past, judging by the comments in lib/sprockets/unprocessed_asset.rb. I think the root problem is that turbo-sprockets-rails3 doesn't cache the list of dependencies, so it can't know when they change.
This library is incompatible with browserify-rails, because dependency modifications do not invalidate the cache.
I'm able to get turbo-sprockets-rails3 to ignore browserify-rails by dropping this line in an initializer, but this has the drawback of removing all benefit from using turbo-sprockets-rails3.
It looks like this was encountered with Sass/Less in the past, judging by the comments in
lib/sprockets/unprocessed_asset.rb
. I think the root problem is that turbo-sprockets-rails3 doesn't cache the list of dependencies, so it can't know when they change.