I have one project that uses rails-assets.org has a source in the Gemfile for loading angular.js, leaflet, and some other javascript libraries. The project has been in production for 6+ months and I haven't had any issues yet.
I've also used bower for managing front-end dependencies in rails and that works pretty well also. It's super simple to get bower and sprockets working together - no need for the rails-bower gem that's out there. I prefer the latter approach because I don't like adding unnecessary dependencies to the Gemfile when I can help it. As for the Webpack approach, I've looked at it, but wouldn't use it in a Rails app. I've learned over the years that it is best to stick as close to Rails as possible, if you're using Rails. However, if a project requires using something like Webpack, because bower+sprockets doesn't cut it, then I'd completely separate the front-end from the backend. e.g. backend being an api app, front-end being an ember/angular/backbone/whatever app. On Sunday, October 12, 2014 5:14:52 PM UTC-7, Benjamin Wanicur wrote: > > Howdy > > Wondering how many of you out there have used this site ( > https://rails-assets.org/) ? It's a way to include asset dependencies > right into your Gemfile without having to use a gem. I've noticed that > often gems packaging assets can have old versions of the assets and are not > always maintained well. This seems like the best of both worlds. Anyone > have any problems with it ? > > Ben > -- -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby --- You received this message because you are subscribed to the Google Groups "SD Ruby" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
