The Journey to Adopting Embroider
summary
Progressive migration to Embroider uses concrete steps: run an Embroider trial build on every merge and gate by tests so problems surface early, then fix incompatibilities and flip the default; tooling stays webpack via asset modules; a surprising ~20 issues crop up and get resolved; public/* assets lose fingerprinting so images must be imported or handled with Embroider macros; enable compatibility shims first (add-on trees, helpers, modifiers, components), then swap to embroider-router for rule-based code splitting and observe measurable payload and rebuild improvements.
AI-written summary · about
chapters (11)
- 0:00Adopting Embroider
- 1:59What Embroider is and why
- 4:52Setting up Embroider in two minutes
- 5:13Safe Embroider at scale
- 6:37Fixing asset fingerprinting
- 9:28Gradual Embroider optimizations
- 10:11Static analysis for tree shaking
- 11:36Apps statically analysis safe
- 13:40Rule-based code splitting
- 14:22Case study sample app
- 15:26Key takeaways
