Who Moved My Cheese? Ember's New Filesystem
summary
Module Unification ships a concrete filesystem: Module Unification (RFC 143 from 2016) gives colocation, namespacing, and addon isolation; code bundling and addon integration are explicit goals. Migration uses deprecations, codemods and the ember-module-migrator plus optional feature flags behind ember CLI canary; generators create MU apps and addons. The fallback resolver and local lookup handle mixed classic/MU ecosystems. A summer 2017 demo worked; recent “golden spike” enables MU app -> MU addon component invocation and the migration tools are usable today.
AI-written summary · about
chapters (7)
- 0:00Introduction and progress
- 4:54Framework change tools
- 11:09File system design
- 17:03Local lookup and isolation
- 20:23Add-on namespace isolation
- 23:30Migration and compatibility
- 25:53Getting started and call
related talks
31mDealing with Data in 2019
24mNew to Ember: What ARE All These Things?
40mEmber's Technical Foundations – And How They Are Changing
01h 11mOpening Keynote
24mMigrating an Existing App to Ember, Component After Component
06mFrom Mainframe to Mainstream: A Case Study in Emberification
23mOctane Octopus: The Multi-Faceted Migration
28mModernizing a Massive Monolith