3 ms·
>Your monorepo would start looking like an artifact repository at some point, with multiple versions of products. It shouldn't, that's one of the big gains of
by joshuamorton 9y ago
>Your monorepo would start looking like an artifact repository at some point, with multiple versions of products.
It shouldn't, that's one of the big gains of a monorepo, is that there's only one version of everything. You don't need to version your dependencies within the repo, which means you only need to maintain one version of any external dependency.
- humanrebar 9y agoI wouldn't call getting every project, internal or external, on the exact same version of every dependency "simple". That's a lot of hand waving around a really hard problem.
- joshuamorton 9y agoIts hard to do if you don't start out that way early on, yes. I don't really think its hard to maintain that state. With multi-repo environments, btw you still need to do that kind of dependency version management for certain upgrades. Essentially you can desync but you have to occasionally re-sync everything. I na monorepo environment you can just prevent desynchronization.
- TheCoelacanth 9y agoIt's a hard problem, but it's not necessarily harder than other approaches to dependency management. There's pretty much no approach to dependency management that isn't hard in one way or another.