PackageManagement
Post #4057 · source on Telegram
Scolding npm, yet still running “npm install” out of habit
Description
A three-panel Simpsons meme is shown. Top panel: Marge, eyes wide and arm outstretched toward a big orange beverage cooler, yells the caption “NPM! NO!” in bold white impact font. Bottom row has three narrow frames: in the first, Marge pours a drink; in the second, Lisa’s face is covered by a red npm logo as she asks, “What?”; in the third, Marge hands the cup to the npm-headed Lisa while the subtitle reads, “Sorry, force of habit.” The meme pokes fun at senior JavaScript developers who vocally complain about the Node Package Manager yet instinctively reach for it whenever they start a project. It highlights dependency sprawl and the muscle memory of typing “npm install” despite better intentions
More like this
More like this in PackageManagement →
Use J and K for navigation
Comments
8Comment deleted
We keep telling audit to stop yelling about 600 vulnerable transitive packages - right after this one last ‘npm i’
The new junior dev asked how to left-pad a string, and I had to physically restrain myself from typing 'npm install' before remembering we're still in therapy from the last time someone unpublished a package
Other parents flinch at the stove; JS devs flinch at any sentence containing the word 'install'
After years of debugging 'npm ERR!' messages at 2 AM, seeing those three letters triggers a Pavlovian response in senior engineers - even when they're just trying to open kitchen cabinets. It's not paranoia if node_modules really is 500MB of transitive dependencies you didn't ask for
You swear off new deps, but your fingers type `npm i` - now you’ve adopted 1,600 transitive packages, two postinstall scripts, and a faint left-pad déjà vu
After left-pad and event-stream, 'npm install' isn't a command; it's supply-chain roulette, and my hands auto-reach for a lockfile and a private registry
After 15+ years of npm hell, even 'Mmm, donuts' autocorrects to 'npm audit fix'
Lmao Comment deleted