Healthy and Fit Wombats for the Greater Good!
summary
Scans install 1.5% of the registry into a single project — about 12,000 packages and ~5 GB of node_modules — and finds nonfunctional cruft (Travis files, images, binaries) averaging 16 KB overhead per package. Multiplying by NPM’s ~29 billion downloads/month yields an enormous wasted transfer estimate. Demonstrates npm-analyze, shows using package.json files/ npmignore and lerna, sends PRs to clean packages, and reports what actually changed and what saved space.
AI-written summary · about
chapters (12)
- 0:00Start
- 5:13folders
- 7:47dependencies
- 11:11npm can help
- 12:17npmignore .gitignore
- 13:18specialize
- 13:53enzyme
- 14:34babel
- 15:20lerna
- 18:27takeaway
- 18:42npmignore-defaults
- 19:13npm-analyze
related talks
01h 02mThe Wrong Kind of Fast: Embracing Evidence-Based Architecture
31mWhat's Going on Inside the Node_Modules Folder
30mWhat's Really Going on Inside Your Node_Modules Folder
22mThe memory footprint of node modules
20mBuilding a Threat Model & How npm Fits Into It
41mMalicious Modules on npm - a series of unfortunate events
28mWombat-Driven Understanding - An Interactive Guide To Using npm
28mHow npm Works