Webpack at Home: The Rails Asset Pipeline

Asking for Webpack and getting the Rails 3.1 Asset Pipeline is the technical equivalent of asking for a Tesla and being handed the keys to a Ford Model T with a hand crank

“Sure, the Rails 3.1 asset pipeline is ‘basically Webpack’ - if your idea of module federation is require_tree . and a silent prayer that Sprockets doesn’t segfault in prod.”

The senior dev who insists the asset pipeline is 'basically the same thing' is the same one who still defends their 2011 decision to store JavaScript in vendor/assets because 'npm is just a fad' - meanwhile, the production deploy takes 45 minutes because Sprockets is trying to figure out if that one CoffeeScript file from 2012 has changed

Ah yes, the Rails Asset Pipeline - where you spend more time debugging why your CSS isn't compiling than actually writing CSS. It's the build tool equivalent of being told 'we have microservices at home' only to discover a 500k-line Rails monolith with a single Sidekiq worker. Senior devs remember when Sprockets was considered 'modern' and CoffeeScript was the future - now they're the archaeological layers we excavate during modernization sprints, right before someone suggests 'maybe we should just use Vite?'

Ask for HMR and code‑splitting; get Sprockets, a manifest, and a 12‑minute rake assets:precompile - true enterprise “Webpack at home.”

“We have Webpack at home” means Sprockets: require_tree ., globals as your module system, digests as a security blanket, and a 12‑minute rake assets:precompile

Senior's Webpack: Rails 3.1 Sprockets, where assets flow through a manifest of madness, fingerprinting grudges since 2011