yeah, I heard that tree's are very hungry this time of year.

the root of all evil

I barely managed to escape

I'm glad you found a way to leaf

(shameless plug} I'm working on this approach combining deps.edn + Babashka: https://github.com/protosens/monorepo.cljc/tree/main/module/maestro If I'm not mistaken, it's also the only approach that allows for exposing different "modules" (e.g. libraries) as Git dependencies for Clojure CLI. In case you find it useful. The core idea is that many hard problems disappear when you have only one root deps.edn for everything.

@mccraigmccraig That series described our monorepo over time, yes. We've been really happy with Polylith, bar a couple of small wrinkles which the Polylith team have been very helpful about and receptive to changes. We're currently working with them on an "external test runner" since we ran into problems with the classloader isolation of the in-process one (much as we had with Boot's "pods" back in the day).

Happy to answer any Qs you may have about our setup!

thanks @UCFG3SDFV @seancorfield 👍

we have a simpler/different wysiwyg approach at work, based on https://github.com/exoscale/deps-modules

we have a bunch of other libs on top of it to make it look&feel like lein, but the root of the monorepo stuff is basically done via deps-modules

it's super easy to retrofit to an existing codebase too, which is a big plus in our case