Effective Dependency Management in JavaScript
summary
Hundreds of interdependent JS files cause breakage when one page forgets a file; this talk lays out five concrete rules: declare dependencies, shim third‑party libs rather than editing them, keep definitions separate from executions so modules are reusable and testable, handle loading asynchronously with callbacks (dependency managers like browser IFI do this), and avoid globals by returning private variables. Examples include a counter split into definition + attach code and shimming plugins that expect Angular UI.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:10Dependencies are always declared
- 1:57Trait #2 3rd party code is shimmed
- 2:41Trait 43 Definitions are separate from executions
- 3:25Dependencies are loaded asynchronously
- 4:11Trait #5 Modules do not rely on globals
related talks
18mFront End Dependency Management
40mDependency Management in MFs
42mSponsored Session: Dependencies: Do's and Don'ts
01h 10mModular JavaScript: Dynamic Dependency Resolution
35mKnowing Your TCO (Total Cost of Ownership)
42mYour library sucks, and why you should use it
25mModern JavaScript
41mThe Future of JavaScript Package Management