Template for a good new topic, formatted with
INFO: Since SonarTS v2.0, TypeScript analysis is performed by SonarJS analyzer v6.0 or later. No TypeScript analysis is performed by SonarTS.
While running sonar-scanner and sending reports to sonarqube developer edition 8.1, I am getting this error and typescript files are not analyzed, this was working on community edition 7.9.1.
SonarTS plugin in sonarqube noe - sonar-typescript-plugin-22.214.171.12459.jar
This log is just a note, that actual analysis will be done by SonarJS plugin. Could you share full logs of analysis to understand why TS analysis is missing?
@Lena @Tibin_George_Kuriyan Possibly related to the same issue I’m seeing
Local Sonar Version - Community Edition Version 7.9.2 (build 30863)
Hosted Sonar Version - Version 7.0 (build 36138)
Sonar Scanner 126.96.36.1994
SonarJS/TS - 6.2 / 2.1
Sonar NPM Module - 2.5.0
Between March 6th and Today, our pipeline is no longer reporting code coverage - either in full or on new code.
We have a multi-module setup for an Angular project that has a root properties file and uses the multi-module for each library and app shipped from this repo
Nothing has changed in our configura…
Has only happened recently, seems others are reporting it here too - I’ve raised a bug on Github too, also included logs
Attaching sonar-scanner logs in debug mode.
Log part where it says typescript analysis is skipped
07:02:26.797 INFO: Sensor SonarTS [typescript]
07:02:26.797 INFO: Since SonarTS v2.0, TypeScript analysis is performed by SonarJS analyzer v6.0 or later. No TypeScript analysis is performed by SonarTS.
07:02:26.797 INFO: Sensor SonarTS [typescript] (done) | time=0ms
List of plugins from the above logs
07:01:04.524 DEBUG: Plugins:
07:01:04.525 DEBUG: * SonarCSS 188.8.131.520 (cssfamily)
07:01:04.525 DEBUG: * Svn 184.108.40.2065 (scmsvn)
07:01:04.525 DEBUG: * SonarPLSQL 220.127.116.1176 (plsql)
07:01:04.525 DEBUG: * SonarScala 18.104.22.1685 (sonarscala)
07:01:04.525 DEBUG: * SonarC# 22.214.171.12483 (csharp)
07:01:04.526 DEBUG: * Vulnerability Analysis 126.96.36.1995 (security)
07:01:04.527 DEBUG: * SonarJava 188.8.131.5288 (java)
07:01:04.527 DEBUG: * SonarHTML 184.108.40.2062 (web)
07:01:04.527 DEBUG: * SonarFlex 220.127.116.111 (flex)
07:01:04.527 DEBUG: * SonarXML 18.104.22.1680 (xml)
07:01:04.527 DEBUG: * SonarTS 22.214.171.12459 (typescript)
07:01:04.527 DEBUG: * SonarVB 126.96.36.19983 (vbnet)
07:01:04.527 DEBUG: * SonarSwift 188.8.131.52 (swift)
07:01:04.527 DEBUG: * SonarCFamily 184.108.40.20606 (cpp)
07:01:04.527 DEBUG: * SonarPython 220.127.116.1151 (python)
07:01:04.527 DEBUG: * Google Authentication for SonarQube 1.6.1 (authgoogleoauth)
07:01:04.528 DEBUG: * JaCoCo 18.104.22.1685 (jacoco)
07:01:04.528 DEBUG: * SonarGo 22.214.171.1249 (go)
07:01:04.528 DEBUG: * SonarKotlin 126.96.36.1995 (kotlin)
07:01:04.528 DEBUG: * SonarTSQL 188.8.131.5234 (tsql)
07:01:04.529 DEBUG: * SonarRuby 184.108.40.2065 (ruby)
07:01:04.530 DEBUG: * Vulnerability Rules for C# 220.127.116.115 (securitycsharpfrontend)
07:01:04.530 DEBUG: * Vulnerability Rules for Java 18.104.22.1685 (securityjavafrontend)
07:01:04.530 DEBUG: * License for SonarLint 22.214.171.124237 (license)
07:01:04.530 DEBUG: * Vulnerability Rules for Python 126.96.36.1995 (securitypythonfrontend)
07:01:04.531 DEBUG: * Git 188.8.131.524 (scmgit)
07:01:04.534 DEBUG: * SonarPHP 184.108.40.20666 (php)
07:01:04.534 DEBUG: * SonarABAP 220.127.116.114 (abap)
07:01:04.534 DEBUG: * Vulnerability Rules for PHP 18.104.22.1685 (securityphpfrontend)
That’s the line where the interesting long starts. So the problem is that most of your TS files are not matching any tsconfig file, we are not analyzing those.
07:03:37.498 INFO: Skipping 157 files with no tsconfig.json
So check that for each TS file there is at least one
tsconfig.json in one of the directories above.