Massive.js
summary
Claims migration to TypeScript + AMD yields real gains: an in‑browser workbench and editor get built, tooling adds refactoring and intellisense, interfaces catch many bugs, and a messy codebase of 200,000 lines becomes fit again. A custom AMD loader plus a CSS plugin and lazy-loading contributions let components stay self‑contained and load only when needed. The move costs months of cleanup but restores speed, testability, and maintainability.
AI-written summary · about
chapters (16)
- 0:00Start
- 2:27Team Foundation Server
- 3:47Azure
- 7:09Our Journey
- 12:49Interfaces at Work
- 17:49TypeScript Type Definitions Typed
- 19:09Growing Pains: Dependencies...
- 20:27AMD to the Resque
- 20:52TypeScript: External Modules TypeScript supports code generation for different module systems
- 21:52AMD Applied - Self Contained Modules
- 22:50Lazy Loading Contributions csharp contribution to
- 25:25Even More Growing Pains Writing JavaScript code in a large project is like carving code in stone -Alex
- 27:18Componentization Reuse TypeScript code as 'binary JS components with a declarations file
- 27:59Dependency Injection
- 28:18TypeScript 0.9 (out real soon)
- 29:04TS Retrospective
related talks
29mJavaScript in JavaScript: Inception
25mShiver My Timbers! Migrating yargs to ECMAScript Modules
34mNode.js: Path to ES6 modules
36mMigrating Babel from CommonJS to ESM
30mShipping Node.js packages in 2025
32mES Modules in Node JS
48mESM: EcmaScript Modules in browser and NodeJS. It's about time!
24mMaking small modules actually work with webpack and npm
