# Getting "circular issues" **URL:** \ **Category:** SonarQube for IDE\ **Tags:** typescript\ **Created:** [April 10, 2025, 3:05pm UTC](https://community.sonarsource.com/t/getting-circular-issues/138624 "2025-04-10T15:05:52Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![aaschlote](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/aaschlote/32/68540_2.png) [@aaschlote](https://community.sonarsource.com/u/aaschlote)\ **Post date:** [April 10, 2025, 3:05pm UTC](https://community.sonarsource.com/t/getting-circular-issues/138624/1 "2025-04-10T15:05:52Z")
Hello all, Since yesterday (09.04.2025), we’ve been seeing some issues in SonarCloud related to cyclic dependencies (e.g. _“This file is part of one cycle involving…”_). However, even though we have the `eslint-plugin-sonarjs` dependency in the repository, I’m not seeing these issues flagged in my local environment (VSCode). Right now the “import/no-cycle” is disabled, but even enabling it, I still can’t see the eslint issue. Do I need to configure something specifically to detect these issues locally using ESLint? The repository of my project is available to see in this [link](https://github.com/digitalservicebund/a2j-rechtsantragstelle). Please let me know if there’s any misconfiguration I might have missed. ---
**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\ **Post date:** [April 11, 2025, 5:09pm UTC](https://community.sonarsource.com/t/getting-circular-issues/138624/2 "2025-04-11T17:09:33Z")
Hi, Welcome to the community! You’re not seeing those issues raised by `eslint-plugin-sonarjs` because… they’re not raised by `eslint-plugin-sonarjs`. Even in SonarCloud. 😅 [Not every rule is run](https://docs.sonarsource.com/sonarqube-for-ide/vs-code/using/rules/#other-rule-types) in [SonarQube for VSCode](https://docs.sonarsource.com/sonarqube-for-ide/vs-code/), but most are.   HTH, Ann ---
**Author:** ![aaschlote](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/aaschlote/32/68540_2.png) [@aaschlote](https://community.sonarsource.com/u/aaschlote)\ **Post date:** [April 14, 2025, 7:44am UTC](https://community.sonarsource.com/t/getting-circular-issues/138624/3 "2025-04-14T07:44:13Z")
Thanks for your message. But for this specific case, how can I see if the issue has been solved locally (even for the ESLint tool or Sonar VSCode extension) before I push my changes? Because neither the ESLint tool or Sonar VSCode extension are showing me this issue. ---
**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\ **Post date:** [April 14, 2025, 11:10am UTC](https://community.sonarsource.com/t/getting-circular-issues/138624/5 "2025-04-14T11:10:33Z")
Hi, Sorry. After I answered you, I followed up internally & it turns out even in SonarQube for VSCode, we don’t run the architecture rules. I pointed you in that direction because they’re not yet included in the docs’ list of un-run rules - they’re fairly new - but I’m going to get that fixed. Sorry for the confusion.   ☹ Ann ---
**Author:** ![aaschlote](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/aaschlote/32/68540_2.png) [@aaschlote](https://community.sonarsource.com/u/aaschlote)\ **Post date:** [April 15, 2025, 1:13pm UTC](https://community.sonarsource.com/t/getting-circular-issues/138624/11 "2025-04-15T13:13:18Z")
thank you, do you have a deadline to fix it? 🙂 ---
**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\ **Post date:** [April 15, 2025, 3:25pm UTC](https://community.sonarsource.com/t/getting-circular-issues/138624/14 "2025-04-15T15:25:02Z")
Hi, Unfortunately, I can’t give you a timeline right now.   ☹ Ann ---
**Author:** ![aaschlote](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/aaschlote/32/68540_2.png) [@aaschlote](https://community.sonarsource.com/u/aaschlote)\ **Post date:** [April 22, 2025, 12:09pm UTC](https://community.sonarsource.com/t/getting-circular-issues/138624/17 "2025-04-22T12:09:39Z")
Hi Ann, Thanks for your reply! I just have a quick follow-up question: We have a scenario where **Component A** imports **Component B** , and depending on certain business logic, **Component B** might also import **Component A**. This circular reference is intentional and expected in our setup. Is there a way to **disable the “circular file imports” warning** specifically for these two files, while keeping the rule active for the rest of the codebase? Thanks again for your help! ---
**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\ **Post date:** [April 22, 2025, 12:24pm UTC](https://community.sonarsource.com/t/getting-circular-issues/138624/18 "2025-04-22T12:24:07Z")
Hi, Yes. "Accept"ing the issue in SonarQube for Cloud should make it go away for you.   HTH, Ann