Ryunosuke Sato

> a good time for an official release of gem +1 for me. @unixmonkey How do you think about this idea?

@drewblas How do you feel about this PR?

> I have not seen the issue in master. Yes, me too. I found the issue on this PR https://github.com/lardawge/carrierwave_backgrounder/pull/293. It seems all builds are broken.

I don't know why it causes, but I found a failing build against ruby-head on master. https://travis-ci.org/github/lardawge/carrierwave_backgrounder/builds/748457937

It looks you have the following config in any place. ``` ruby config.app_generators.javascript_engine false ``` Or `--javascript-engine false` option is passed to generator. Please try: ``` $ bundle exec rails...

I prefer throw error with message including available options if invalid option is given. By the way, where do you configure `config.app_generators.javascript_engine` ? Or caused by other gems?

Thanks, I see. It can't be avoided. If you would be interested in matter, would you mind sending a PR?

I changed the way to manage bundled files https://github.com/emberjs/ember-rails/pull/448. Then it stop copying `ember-data.js.map` to `tmp/ember-rails`. I think it will fix this issue. Could you try using [[email protected]](https://rubygems.org/gems/ember-rails/versions/0.16.4) after cache...

Sorry to my late reply :< I'm a maintainer of this repository. Certainly, I have no enough time to support the new feature. (such as Babel 6 support https://github.com/babel/ruby-babel-transpiler/pull/282 )...

Thanks for your reply, @yob. Okay, I missed that puma supports older Ruby versions. I'm keeping this PR as opened.