4 ms·
There's a second option, not mentioned by the sibling comments so far: Publish the library somewhere (e.g. an internal Nexus) and then have the other consumer p
by codethief 1y ago
There's a second option, not mentioned by the sibling comments so far: Publish the library somewhere (e.g. an internal Nexus) and then have the other consumer pin the old version of the library instead of referring to the newest version inside the monorepo. Whether or not this is acceptable is largely a question of ownership.
- cloogshicer 1y agoThanks for your response! Don't you lose the main advantage of the monorepo then, since you can no longer rely on the fact that all the code at any one commit in history fits together? Or are there other significant advantages that still remain?
- codethief 1y agoSee my response to your other comment in a sibling thread: https://news.ycombinator.com/item?id=44120854 https://news.ycombinator.com/item?id=44120854