Hello! I'm Ross. I build web apps.

My name is Ross Kaffenberger. I'm a principal engineer at Stitch Fix.

I teach full stack web developers about the frontend tools and performance, especially at the intersection of JavaScript and Ruby on Rails.

Need help with webpack and Webpacker? That's my jam.

Check out my writing, talks and projects. You can also connect with me on GitHub, Twitter, and Medium.

Join the Newsletter

Please enter your email address to get an occasional email about JavaScript, Ruby, and the web. Thank you!

    Powered By ConvertKit

    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.

    Understanding your Rails webpack configuration and build output can be a little confusing, especially if you're new to either Rails or webpack. This post contains a few tips for debugging your Webpacker setup, some specific to Rails Webpacker, some generally applicable to webpack.

    Configuring webpack is precisely the main job of Webpacker's NPM package, @rails/webpacker. This post provides an overview of how to customize its default settings for your Rails application.

    Configuring Webpacker can be a daunting task. In this guide, we will take a look at the options provided via the webpacker.yml file and supported environment variable overrides.