--- title: "Fixing Angular Standalone Components that have a circular dependency" url: https://daily.dev/posts/fixing-angular-standalone-components-that-have-a-circular-dependency-zwqmkycz1 source_url: https://timdeschryver.dev/blog/fixing-angular-standalone-components-that-have-a-circular-dependency type: article source: "Tim Deschryver" author: "Tim Deschryver" published: 2026-05-31T07:47:33.830Z updated: 2026-06-01T04:01:33.601Z tags: ["typescript", "angular"] reading_time: 3 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Fixing Angular Standalone Components that have a circular dependency **[Tim Deschryver](https://daily.dev/sources/timdeschryver)** · [@timdeschryver](https://daily.dev/timdeschryver) · 3 min read · 0 upvotes · 0 comments ## Summary When migrating Angular projects to use Standalone Components, circular dependencies between recursively rendering components cause runtime errors. The fix uses Angular's `forwardRef` function from `@angular/core` in the child component's imports array, allowing it to reference the parent component before it's fully initialized — avoiding the need for a full refactor. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: --- Tags: [#typescript](https://daily.dev/tags/typescript), [#angular](https://daily.dev/tags/angular) [View this post on daily.dev](https://daily.dev/posts/fixing-angular-standalone-components-that-have-a-circular-dependency-zwqmkycz1)