3 ms·
The point is so you can do single commit cross project changes. You also have the added benefit of being able to track exact code/dependency versions across al
by jayd16 6y ago
The point is so you can do single commit cross project changes. You also have the added benefit of being able to track exact code/dependency versions across all projects.
In a many-repo, dependency tracking set up, its an anti-pattern to pin to latest because that can change underneath you and its hard to know what version latest even meant at the time someone committed the dependency.
In a submodule setup, you can track exact dependencies but you pin each submodule reference. You can't easily update all downstream references. You can't use latest for reasons above. You also can't make single commits across many projects.
In a monorepo set up, you can point to latest (ie whatever is in any given HEAD) and trust that everyone will know exactly what that means now and into the future. Monorepo also opens up some ability for build systems across projects and possibly more insight into company wide dependency tracking.