refinerycms-core depends on coffee-rails, forcing JS runtime to be needed

[krbullock]

The refinerycms-core gem depends on coffee-rails, which in turn depends on execjs. This makes it impossible to deploy a Refinery app to a production server without a Javascript runtime. It probably also means that if you just uncomment the therubyracer dependency in the assets group, then try to deploy using bundle install --without development:test:assets, execjs won't be able to find a runtime.

I imagine that the coffee-rails dependency is there because the app generator is in -core, but does generating an app really require coffeescript? It seems like that would only be needed when compiling assets.

If the dependency can't safely be removed, the things in -core which require it could be moved into a separate gem that can require coffee-rails, leaving -core with no dependency on JS.

[parndt]

We need it for the coffeescript files. But it only needs to be in the
assets group of the app's Gemfile. Could you please fix this for
master? You will need to update the edge template.

[ugisozols]

Merged in 6f0ee74.

[ilikepi]

Is there any chance this could be backported into 2-0-stable? It's rather inconvenient that the latest gem release still has this dependency, and the change itself seems simple enough.