Migrating an Existing App to Ember, Component After Component
summary
Migrates a legacy server rendered app to Ember incrementally, replacing UI pieces until the page becomes an Ember app; avoids a 6–18 month big bang rewrite by bootstrapping components with a JSON descriptor, setting location to none and rootElement, and exposing a tiny imperative API and events for host communication. Uses ember-cli + ember-islands + visit API + services to build and ship parts, followed sequence facets first, then search, then data table, and reports the approach works though the data table integration is still in progress.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:12Migrating an app to Ember COMPONENT AFTER COMPONENT
- 2:21You can't always start over
- 3:28The outside world is hostile
- 4:46Your app is just a component
- 6:56Integration strategies
- 11:55Bootstrapping
- 14:57Ember Islands
- 15:57Communication
- 19:07Build process
related talks
25mThe Chirpolith: Successfully Migrating a Messy App to Ember
22mUsing Ember to Make the Seemingly Impossible Easy
22mUsing Ember to Make the Seemingly Impossible Easy
46mArt and Science of Shipping Single Page Apps with Ember.js
25mTwo Ember Apps Become One
32mAnimations and Transitions in an Ember App
29mThe Art of Ember Deployment
36mPanel: Ember at Scale