A case study of Rails applications making a common Webpacker mistake of rendering modules multiple times on a single page. We'll describe why the problem happens and present a Webpacker Packing Checklist for proper code-splitting.
Hello! I'm Ross. I build web apps.
My name is Ross Kaffenberger.
I help backend and full-stack developers learn the frontend. Why? Ruby on Rails uses JavaScript too.
Check out my recent posts, series, talks, and projects. You can also connect with me on GitHub, Twitter, and Medium.
Navigate the world of Webpacker and webpack on Rails with confidence using this collection of mental maps I put together.
When running Rails system or integration tests, you might be surprised to learn that Webpacker will load your development webpack config. What's the deal?
In this post, we'll take a look at installing and using the webpack-bundle-analyzer, perhaps the most invaluable webpack plugin, to analyze and debug the output of the webpack build in a Rails project configured to use Webpacker.
A new Rails 6 application will install both Webpacker and Sprockets by default. Don't they solve the same problem? This article dives into why Sprockets lives on even though webpack has surpassed most of its features and why you might want to choose one over the other.