Webpack, although a little hard to configure, remains the leading edge build tool for modern web development. This post/video guides you through adding Webpack to an older Ruby on Rails 5.2 project as well as the latest Ruby on Rails 6 beta release.
The demos here are meant to be a high-level overview of how Webpack can be used inside Ruby on Rails no matter the version.
With Webpacker you gain these features and more:
- webpack 4.x.x
- ES6 with babel
- Automatic code splitting using multiple entry points
- Stylesheets – Sass and CSS
- Images and fonts
- PostCSS – Auto-Prefixer
- Asset compression, source-maps, and minification
- CDN support
- React, Angular, Elm and Vue support out-of-the-box
- Rails view helpers
Realistically, in most cases, you don’t but it does make it easier to reach for modern front-end frameworks like Vue.js or React.js with minimal setup time. The asset pipeline still works as it should alongside the new webpack workflow. All assets associated with webpack now live inside an
The webpacker gem doesn’t depend on the asset pipeline directly though it does hook into a few rake commands bundled with each Rails installation
app/assets/ for any
css, images, or other assets the project I’m working on might require.
Realistically, no but the asset pipeline has a bunch of handy features for rendering assets in views you or your team may be accustomed to. Luckily you can do the same with assets inside
Want to learn Ruby on Rails from the ground up? Check out my upcoming course called Hello Rails.