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.
Please let me know if there’s any misconfiguration I might have missed.
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.
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.
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?
