4 ms·
Then you're not using a monorepo. The whole point of a monorepo is that everything is using the most recent version of every dependency, always. If they don't,
by bananabreakfast 5y ago
Then you're not using a monorepo.
The whole point of a monorepo is that everything is using the most recent version of every dependency, always. If they don't, then you broke the build. Versioning does not exist, dependency hell does not exist, everything works together. Dependencies are simply imported and atomic commits upgrading both client and server are possible.
If you need to use an old API for a dependency, then that is a new dependency that is added to the monorepo as a separate project that you now have to maintain.
There are plenty of downsides too, but these are the advantages and the reasons why Google had no incentive to design a good module system for Go v1.0.
- tsimionescu 5y agoThis is such a strange take. It's always simpler to have a single repo rather than multiple repos, especially if using something like SVN or P4 where you can easily clone or branch a single directory. So regardless of how you develop and how easily you can use latest vs known-safe builds, there may just not be any down-sides to a monorepo, depending on your VCS.