Monorepo Support
I don&#x27;t get the case against monorepos, and why it&#x27;s so polarizing.<p>You can share code without having to stand up infrastructure to host packages and whatnot.<p>You can separate concerns without introducing the infinite complexity of network io, queues etc. This is kind of a dig at microservices I guess, which have their place functionally (decoupled infrastructure, scaled independent of other services).<p>You can still deploy to separate targets, a code repository is not 1:1 with a deploy target, that is a fake constraint that never even existed.<p>Manyrepos ALWAYS end up being second class citizens. Test setup isn&#x27;t as good as in the monorepo because that means duplicating it N times, and that is obviously wrong.<p>Common patterns are The Same But Different everywhere and&#x2F;or there is crazy complexity in sharing code between repositories to alleviate this (often having its own problems)<p>It&#x27;s just... all of that goes away with one&#x2F;fewer code repositories. So... why? I&#x27;m not even anti micro-service, monorepo actually makes MORE sense with microservices IMO. Why do we do this?<p>Before someone points it out, I do recognize that a monorepo can still be poorly architected. We can all rest assured knowing that poor architecture is poor architecture whether it be monorepo, manyrepo, monolithic, microservice,  PHP, Rust, blah blah.