> With a monorepo, it’s more tractable.
Is it really though? Sure, it's technically possible, but it feels like a massive burden to place one on dependency.
Not only do you have to maintain your own lib, but you have to understand how every other project uses it.
It’s still not scalable in the sense that the downstream can make any change they want. They are restricted to changes they can either manually or automatically apply to client code in a reasonable amount of time. But that’s the trade off for being a heavily depended on library (which a lot of the time is an explicit decision).