npm install via https://github.com/thdk/package-changed?tab=readme-ov-file#use-git-hooks-to-run-package-changed-automatically with post-checkout, post-merge, and post-rebase. To be specific about how this works (for those who haven't uses package-changed) it checks if your package.json (and optionally package-lock.json) has changed by storing a hash and checking against that hash to determine if npm install needs to run. This is relevant to what Theo mentions around the 7:50 mark in today's video. With this in place (assuming a clever dev hasn't /dev/null'd husky) the problem of pulling new commits that include changes to dependencies for the most part goes away. It's not a substitute for CI by any means and shouldn't stop anyone from working. It's just meant to be a gentle assist.
