Organizing and Packaging Rich Javascript Apps with Ruby
summary
rake pipeline packages client JS as a real build system by turning filters into incremental file tasks so builds skip unchanged files and stay fast. Filters are simple Ruby subclasses with generate_output, common ones include uglify (via the uglifier gem), a closure wrapper, a concat step that emits application.js in dist, and a CoffeeScript matcher that compiles into the pipeline. Commands are rakep build / clean / server; a middleware and Rails 3 tie let the dev server and deployment workflow work as described.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:17JavaScript build systems evolution
- 3:23Rake Pipeline purpose
- 4:49Rake Pipeline with Rake
- 5:54JavaScript pipeline with Rake
- 7:39Ruby DSL and helpers
- 8:43CoffeeScript with matchers
- 9:24Rake Pipeline commands
related talks
34mFrom Sprockets to js-bundling: Evolution of JavaScript tooling in Rails!
29mAggregation with Sprockets
54mBuilding and Managing a Ruby Infrastructure
29mRails Asset Pipeline: Defunct or Da Funk
01h 12mRuby Best Practice Patterns
25mMAKING JAVASCRIPT GREAT AGAIN IN RAILS
21m6 degrees of JavaScript on Rails
32mAs easy as Rails