Honey, I shrunk the node_modules!
summary
A case study showing how the node_modules folder was reduced threefold in a JavaScript project to improve application and development performance. Covers measured impact of node_modules size on performance, techniques used to shrink dependencies, and whether package authors pay attention to package size; aimed at intermediate developers.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:44node_modules problem
- 11:33Why node_modules is huge
- 20:12Analyzing dependencies
- 26:10Finding problematic packages
- 31:57Removing unused files
- 37:57Production version optimization
- 40:25Benefits of dependency control
related talks
39mThe Structure of Node.JS Applications
22mThe memory footprint of node modules
16mThe future of Node dependency management
31mDivide and conquer: using NPM to scale you codebase
48mThe Node Module Diaries: Large App Architecture from the Trenches
33mHoney, I shrunk your Ember app
02h 24mHow to Node.js - Part 2
58m10KB or Bust: The Delicate Power of Webpack and Babel