Governing npm Dependencies Across a Monorepo

If you've been following my Pedalboard monorepo journey, from setting it up from scratch , to migrating from Yarn to pnpm , to bringing in Bazel for builds. You know that a monorepo is a living thing. You add packages, tweak configs, and things evolve. That's the whole point. But here's the thing that sneaks up on you: dependency drift. You start with good intentions. Every package pins the same version of typescript . A few months later, one package got bumped when you fixed a bug, another one