# verbose output
`-Sdeps '{:aliases {:verbose {:verbose true}}}' -A:verbose`



# timing the download of dependencies if there are issues
`time clj -Spath -Sforce`


# Switching to a monorepo
All internal libraries are `:local/root`. Makes working in the REPL great (elaborate)

Constraints when switching:

- We use CircleCI for CI/CD. There's no support for monorepos with CircleCI. This leads to longer build times - every project runs through its test steps with every push. We recently switched to their new unlimited parallelism plan which has been quite helpful in getting CI time down.

- CI configuration was moved into a set of clojure files because it became far too tedious messing around with YAML with the number of projects we have. This does, unfortunately, mean that CI config needs to be manually generated with a command every time you change the CI clojure files.

- We have a small service diff library that detects when a particular service's code, deps.edn, or `:local/root` deps have changed. That ensures a service won't get deployed on every push.

- We don't have a great way to have a common deps.edn across all projects. This would be quite useful for things like: global exclusions (when supported), overriding certain library versions, common aliases, etc. Ideally there'd be some way to just pass in N number of deps.edn files to `clj` and have it merge those in. Any editor environment would also need to have some way to select which deps.edn files to use (like CALVA)

- We don't have a good way to run commands across all projects or only in a certain project. For example, I'd like to be able to do something like: `monorepo my-service uberjar`.

- Ensure consistant alases for running tests and other tasks
Different libraries & services run tests with a different set of aliases. Every time we want to run the tests for a project, you need to go to the projects README (or check the CI config) and determine which aliases to use to run the tests. Either the aforementioned "command runner" or a way to combine aliases somehow would make this much better.

Overall, this workflow is *far* better than having individual repos and constantly needing to restart the REPL when working across projects.