Replacing the Rails Asset Pipeline with Webpack and Yarn

23/11/2016
2.808

Ruby on Rails has a pretty sweet ecosystem. We have libraries for everything from printing a table flipping emojicon on an exception to natural language processing. Just add the desired libraries to your Gemfile, type bundle, and you’re on your way (ahem. Usually).

When it comes to dealing with JavaScript libraries in a Rails project, however, things aren’t as straightforward. Should you download the Javascript code and manually store it in the /vendor directory or look for a wrapper gem that’ll just make the bad Javascript man go away? If you install the libraries manually, it’s up to you to ensure all the dependent libraries are also installed.

Replacing the Rails Asset Pipeline with Webpack and Yarn #ruby #rubydeveloper #rubyonrails #asset #webpack https://rubyonrails.ba/single/replacing-the-rails-asset-pipeline-with-webpack-and-yarn