Rails Assets: frictionless proxy between Bundler and Bower

http://szymon.hussa.rs/vggG

by szymo • 13 years ago

41 10 13 years ago

szymon.hussa.rs

timdorr• 13 years ago

Sprockets has had native Bower support for some time. In Rails 3.x, there is a version restriction that prevents upgrading to the latest version, but there is a 2.2.2.backport2 version you can use to get at all the new features: http://stackoverflow.com/questions/16266528/how-to-manage-ja...

You can add a .bowerrc and bower.json file to your project and you'll be able to access those components easily: http://dev.af83.com/2013/01/02/managing-rails-assets-with-bo...

teamon2• 13 years ago

There are various solutions to managing assets in a rails application but we didn't like any of them. The one you linked to requires having separate list of dependencies and using bower directly which means hacking standard rails deployment.

bigtunacan2• 13 years ago

Love it. Keeping JavaScript libraries up to date in Rails can be a real pain and the sprockets solution just isn't all that great. I like how you have approached this with a dead simple approach to implementation and integrating with the existing tooling (bundler/Gemfile). Good work!

lucisferre• 13 years ago

Thanks you guys, as someone who's been using Bower with Rails for a while I can tell you this was badly needed. I played with your project about a month back and really liked where it was heading. I'm looking forward to giving it another spin today.

joshpeek2• 13 years ago

Most the issues under "bower is a mess" are being discussed in the https://github.com/bower/bower.json-spec repo. I have a number of proposals to improve the "main" directive and other require paths.

There is a strong dissenting opinion in bower community that it should basically be just like "npm" and none of these structured require build tool hints should be encouraged. It'd be great if others in support of the current Sprockets bower integration or this Rails Asset tool to voice their opinion and real world use asset for improving the state of the bower.json manifest.

Thanks, Josh, author of Sprockets.

teamon2• 13 years ago

While we all know that ruby gems have a couple of issues I think one thing was done exactly the way it should be - somehow enforced standard structure: NAME.gemspec, bin, ext, lib, lib/NAME.rb. I don't know if this is specific to only ruby community but there is at least some level of consistency which makes everyone lifes easier.

I will have to carefully read all arguments agains enforcing such structure in bower.

bradgessler• 13 years ago

We solved this problem with https://github.com/polleverywhere/sprockets_bower in a simpler way.

This reminds me that bundler could handle dependency resolution beyond gems. Imagine:

  gem "rails"
  gem "coffeescript"
  bower "jquery"
  bower "backbone"

Run bundle and all the dependencies get mapped out and installed.

damncabbage• 13 years ago

One question I haven't managed to answer yet: what happens when a Bower-bundled component needs to use and image (or a font)?

As far as I can tell, there's not asset-path() usage, and so the link breaks in production (where image assets have <assetname>-<md5hash>.jpg filenames, for example).

Rails Assets: frictionless proxy between Bundler and Bower

Related Stories