From Sprockets to js-bundling: Evolution of JavaScript tooling in Rails!
summary
Timeline traces Prototype/Scriptaculous → jQuery → Rails 3.1 sprockets/asset pipeline (adds bundling, digesting) → Turbolinks → rise of React + Babel + Webpack → Webpacker (later Shakapacker) → ES modules and import maps and Hotwire → option of JS bundling and CSS bundling with esbuild/rollup for heavier apps. Recommendation: use import maps for simple monoliths, JS/CSS bundling for moderate JS needs, Shakapacker or API+SPA for very heavy React single‑page apps.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker intro
- 1:08Rails JavaScript tooling overview
- 2:57Pre-asset pipeline era
- 8:18Asset pipeline and Sprockets
- 12:10Turbolinks and modern interactions
- 13:54Rise of React and Webpack
- 18:28Webpacker and its challenges
- 21:17HTTP/2 and JavaScript evolution
- 23:46Import maps and Hotwire
- 26:11JS and CSS bundling alternatives
- 27:37Choosing the right approach today
- 29:01Q&A on admin templates and Rails APIs
related talks
25mMAKING JAVASCRIPT GREAT AGAIN IN RAILS
23mRails Frontend Evolution: It Was a Setup All Along
17mWebpacker vs Asset Pipeline
31mReact on Rails
36mFront-End Sadness to Happiness: The React on Rails Story
25m"React integration into existing Rails applications"
45mBundler Bonanza
29mRails Asset Pipeline: Defunct or Da Funk