Monorepos offer one thing, and precisely one advantage, "visibility" because everything is in the same place, you can, in theory can find stuff. However in pr

Monorepos offer one thing, and precisely one advantage, "visibility" because everything is in the same place, you can, in theory can find stuff. However in practice its also a great way to hide things. But the major issue is that people confuse monorepos for a release system. Monorepos do not replace the need for an artifact cache/store, or indeed versioned libraries. They also don't dictate that you can't have them, it just makes it easier _not to_. You can do what facebook do, which is essentially have an unknowable npm like dependency graph and just yolo it. They sorta make it work by having lots of unit tests. However that only works on systems that have a continuous update path (ie not user hardware.) It is possible to have "atomic changes" across many libraries. it makes it easier to regex stuff, but also impossible to test or predict what would happen. Its very rare that you'd want to alter >0.1% of the files in your monorepo at one time. But thats not the fault of a monorepo, thats a product of having millions of files.