Does it make sense to analyse typescript 4.9.5 code with SonarQube EE 8.9.6?

I’m hoping that the title is explicit enough, but to add some more details, we recently migrated an angular application from Angular 8 to Angular 15, with typescript going from version 3.5.3 to version 4.9.5.

We had a SonarQube analysis set up for the versions using Angular 8 and since the migration, that analysis doesn’t bring up any Code Smells at all, which we find suspect since some of the ones that existed before haven’t been corrected. We’ve tried changing the NodeJS version used by sonar-scanner to NodeJS 14 and 16, but it didn’t change anything. There are also no errors at any point during the analysis.

Checking out the documentation for SonarQube 8.9, it seems that it simply doesn’t support Typescript 4.9, but since the documentation for SonarQube 8.9 ( only mentions a version (4) and not a range, it’s not clear to us that this is the problem.

So, is that actually the problem and it can only be solved by upgrading SonarQube, or are we missing something else there ?

Hey there.

SonarQube v8.9 LTS maxes out support at TypeScript 4.2.

SonarQube v9.9 LTS supports Typescript 4.9.

SonarQube v10.1 will support Typescript 5.

Sounds like an upgrade is in your future. :slight_smile:

1 Like