[prepperdev]

Monorepos are underappreciated.

- Dealing with cross-repositories changes is unproductive.

- Relying on external servers (git / npm / whatever) is risky.

- Visibility of what goes to your servers is never easy without having everything in one (well-organized) monorepo.

Monorepos solve it all, without adding any issues, if done right.

[pards]

Is there a good solution for only building the projects that have changed? We looked at bazel.build but found it to be too complex.

[randymarsh77]

CI systems (or surrounding community) typically give a mechanism for “last successful commit”. Executing a diff of changes and detecting from that which projects should be built from is something you can build using that data. If you have a lot of interconnected project dependencies in a mono repo, this logic might be more challenging to write, but there it is.

[elcomet]

One common issue is that build can be very long if you rebuild all the apps from your monorepo