Front End Dependency Management

on YouTube ↗18m

" summary

Compares two concrete setups: RequireJS + r.js for async module loading and build-time bundling (development shows one HTTP request per module; r.js produces a single prod bundle), versus Browserify + npm for CommonJS-style requires, bundling, and easy reuse between server and browser. Notes npm tracks deps in package.json via npm install --save, supports transforms, and Browserify bundles synchronous requires. Gives a live use case: lazy-load view when cursor is within 200px and recommends choosing based on app constraints.

AI-written summary · about

" chapters (15)

1. 0:00Introduction and welcome
2. 1:05Front end dependency management overview
3. 2:29Problems with old dependency methods
4. 3:53Benefits of modern dependency management
5. 4:34Key features for dependency tools
6. 5:57AMD vs CommonJS vs npm overview
7. 6:40AMD and RequireJS explained
8. 8:24Browserify and CommonJS explained
9. 10:55Hybrid dependency pattern
10. 12:41AMD vs Browserify differences
11. 14:48npm integration benefits
12. 15:31Limitations of RequireJS and Browserify
13. 16:13AMD vs CommonJS debate
14. 16:56ES6 modules future
15. 17:17Conclusion and recommendations

" related talks

• 19mMaking front end modules actually workLin Clark · EmpireNode 2015
• 30mPackWars: Webpack vs Browserify vs SystemJS vs require.jsOpher Vishnia · Render Conference 2017
• 05mEffective Dependency Management in JavaScriptHector Virgen · Fluent Conference 2015
• 26mA tale of two front-end development environments: or how bend npm3 to your willKate Hudson · npm camp 2016
• 46mIn this JavaScript tooling jungle, a return to simplicity is...Hubert Sablonnière · Devoxx France 2021
• 36mUnbundling the JavaScript module bundlerLuciano Mammino · Codemotion Rome 2018
• 49mFront Ends for Back End DevelopersMatt Raible · Spring I/O 2017
• 17mBundling your Front-End with webpackSandeep Singh · NDC London 2017