Upgrading jQuery plugins to work with Webpack is a common source of confusion. If you're lucky, you may find they can work in either context such that you might not need jQuery at all.
There are plenty of great reasons to switch to Webpacker, including improvements in supported syntax, development tooling, performance optimizations, and more. For Rails developers considering the upgrade from the Rails asset pipeline, start here.
A reference guide to NPM version constraints for dependencies declared in the package.json file of a Rails project from the perspective of a Ruby developer familiar with similar conventions used to specify Ruby dependencies in a Gemfile.
When I first started working with Webpack, I was in for a few surprises. I assumed how things should behave, based on my previous experience with the Rails asset pipeline, only to learn through experience how I was wrong.
Tutorial for integrating Bootstrap 4 with Rails and Webpacker 4
This tutorial demonstrates how to create Vue.js components that can render PDFs along with tools like Webpack, PDF.js, and the canvas element.
In this post, we describe the challenges we faced while replacing the Rails asset pipeline with Webpack, how we solved those issues, and what we learned along the way.
Described how I added a Service Worker script to rossta.net with some considerations concerning cache-busting strategies and deployment
Explaining how to integrate the Webpack asset management tool with the Ruby static web framework Middleman