How does AngularJS handle circular dependencies in large-scale architecture?

AngularJS handles circular dependencies poorly by default, requiring architectural refactoring or lazy resolution using $injector.

Circular dependencies occur when two or more services depend on each other, directly or indirectly. AngularJS injector resolves dependencies at runtime, so circular references break the dependency graph. To handle this, developers use patterns like lazy injection using $injector.get(), event-based communication, or extracting shared logic into a third service. In large-scale systems, circular dependencies indicate poor module boundaries and should be eliminated at design level.