Octane Octopus: The Multi-Faceted Migration
summary
A concrete, four‑phase migration lets a codebase adopt Octane incrementally while continuing feature work: upgrade to Ember 3.16 LTS, opt into Octane features, run the community five codemods (component co‑location, angle‑bracket syntax, no‑implicit‑this, ES5 getters, native classes), then convert classic classes to glimmer components with tracked properties, modifiers and @classic scaffolding. Applied across three apps and nearly 50 add‑ons, the approach preserves runtime behavior and keeps the team productive throughout.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:33The Octane Octopus
- 2:10Why Is the Migration Experience Itself Important
- 3:28Primer
- 7:03When Are these Octane Features Available
- 8:49Starting an Octane Migration
- 9:29Enable Octane Features
- 12:51Classic Decorator
- 16:45Preliminary Component Refactors
- 17:54Migrate Action to on and Fn Modifiers
- 19:22Start an Octane Migration
- 20:11Recommended Octane Migration Guide
- 20:26Classic versus Octane Cheat Sheet
- 21:35Key Call Outs
