> It never occured to me that we can do it this way. Requires some thorough > thinking but I love the idea.
this is part of our nimble requirements and lockfiles before we can move to it, that we can use a monorepo seamlessly - it applies equally to many of our own projects - it'll take some figuring out because the "git version" of a library will no longer be the "most recent commit" but rather "the most recent commit of the most recent change in the library + any deps that library has" \- it requires that each library declares its dependencies explicitly (or implicitly via some mechanism, but it must be deterministic). It gets really interesting with go's "minimal version upgrade" strategy which avoids changing dependencies unless explicitly asked for.
