Keynote Part 2
summary
Polaris moves Ember to standard npm packages so add-ons become normal libraries with a v2 add-on format and shipped TypeScript types; a new build architecture called embroider outsources bundling to webpack (or rollup) to enable reliable tree shaking, faster builds, and earlier import errors; templates gain imports via the gjs file format and template tag so components and helpers are real module values; migration is incremental and embroider can translate legacy v1 add-ons at build time.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:14EDITING NOTES
- 1:40PACKAGES HOW DO THEY WORKT
- 2:14HOW IT ALL BEGAN THE "SCRIPT" IN JAVASCRIPT
- 4:09JAVASCRIPT MODULES THE NATIVE MODULES SYSTEM
- 5:31EMBERBUILD PIPELINE OUR ANSWER TO THE MISSING PIECES
- 15:18ADDONS TODAY PUBLISHED AS DYNAMIC BUILD INSTRUCTIONS
- 16:28ADDONS IN POLARIS PUBLISHED AS UMIVERSAL PACKAGES
- 17:48STANDARD IMPORTS NODE PACKAGE RESOLUTION
- 19:53A NEW BUILD ARCHITECTURE
- 21:14TREE SHAKING LAZY DEPENDENCY INCLUSION
- 22:54A PLUGGABLE BUILD ARCHITECTURE
- 24:12TREE SHAKING TODAY COULD IT BE DONE?
- 25:27EMBROIDER ENCODING EMBER CONVENTIONS
- 27:18TEMPLATES TODAY NAME BASED RESOLUTIONS
- 29:59TEMPLATES IN POLARIS VALUES EVERYWHERE
- 33:45GUIDINGPRINCIPLES ALIGNING WITH MODERN PACKAGES
