We are thrilled to announce that the wait is finally over: SonarCloud now supports Dart! (Early Access version). This has been a long time coming, with the first community request dating back to August 2019. Your valuable input through surveys and the numerous +1s in the community thread has been instrumental in making this happen and getting us to this point of an Early Access version. Thank you for your unwavering support. Please note that support for Dart will be available exclusively with SonarCloud Team and Enterprise plans, as well as for Open Source projects.
This Early Access release of Dart support may not include hundreds of rules, but we have focused on delivering the most anticipated ones. Here’s what you can expect:
Support for loading coverage data provided by LCOV
70+ rules, including the iconic Cognitive Complexity
Support in SonarLint and SonarQube will come later. We first want your feedback on this Early Access version and to increase the number of rules.
We are eager to hear from you, so don’t hesitate to reach out if you encounter any issues. Positive feedback is also welcome!
We are using a self hosted Sonar installation and our product is not open source, so if I understand Alexandre’s note well, we wont be able to use the feature?
You will be able to scan your Dart code with an on-prem Sonar installation. Just wait a couple of additional months, and we will include it in a release of SonarQube (the exact version is still under discussion).
I confirm that you need to migrate from your old paid plan to the new Team plan to use the Dart analyzer. If you can’t right now but want to try the Dart analyzer, SonarCloud offers a 14-day trial, so you can create a new organization just for that purpose.
Automatic Analysis considers Dart as a supported language whereas we know that in this context (without knowledge about your dependencies), the results are not that good. We are going to deploy a fix to really exclude Dart from Automatic Analysis. You can also do it yourself by going into Administration > Analysis Method and turn off Automatic Analysis. Update 2024-09-17: the fix was deployed.