This doesn't solve the higher level problem. If you depend on A and B and both depend on C, you now have the npm2 style heirarchy of nested dependencies. As w

This doesn't solve the higher level problem. If you depend on A and B and both depend on C, you now have the npm2 style heirarchy of nested dependencies. As with all 'use submodules' solutions, the devil is in the detail with the nested heirarchy of dependencies and version resolution. I mean, fwiw, its quite nice for simple 1-level-deep dependencies, but this isnt a simple problem. What if A -> C@1.1.5, and B -> C@1.1.9. Do you install both? Only one? You might still be able to solve it somehow, if the submodules are required to have semantic version tags on their versions, you parsed the entire hierarchy and then resolved conflicts (somehow), based on the semver semantics... I guess?