Okay, cool! Do you use the master branch or the issue-66 branch?

How many lines of code is the workspace? (you can type ‘poly info :loc’ to view that).

we're using the master branch, poly info :loc says 19,165 loc

Ok, cool.

What is this issue-66 branch?

The issue description captures the details well : https://github.com/polyfy/polylith/issues/66

Work on resolving issue 66 is ongoing in the issue-66 branch : https://github.com/polyfy/polylith/tree/issue-66

Some more info on progress in the Github project : https://github.com/polyfy/polylith/projects/1

In the beginning, the tools.deps CLI tool supported relative :paths like “../../components/comp1/src” but since some time ago, this produces a warning. Alex Miller opened the https://github.com/polyfy/polylith/issues/66 and explained that this support will be dropped in the future. I’ve been working with solving this problem since then in the https://github.com/polyfy/polylith/tree/issue-66. So far I’ve recommended people to use the master branch, and the reason is that I will introduce a couple of breaking changes in the issue-66 branch, which you will have to manage manually, like small changes to workspace.edn . The internals format returned by the ws command will also change. Some people, like @U04V70XH6 are already using the issue-66 branch. The issue-66 branch uses :deps and :extra-deps to specify dependencies to bricks (components and bases) but also supports :paths and :extra-paths as before. You also get rid of the warnings from the tools.deps CLI tool. So if you want to be on “beading edge” then :issue-66 is for you (if you are also okay with using the tools-deps CLI tool, e.g. “clj -M:poly info”, because the poly tool is based on the main branch).

I’m in the process of migrating a bunch of repos to a single Polylith so those are important information and insights thanks, I think I’m gonna stick to master for now.