We have a similar problem where we have started getting the error ‘You are using version of TypeScript 2.6.2 which is not supported; supported versions >=3.2.1’. Our package.json shows typescript version as “typescript”: “~3.2.4” so I’m not sure what the problem is. I have searched our entire proj…

Ok, now I see what’s happening. We trying to find TypeScript location and happen to find the wrong one (transitive) first. I created a ticket https://github.com/SonarSource/SonarJS/issues/1928 to fix this problem. As a workaround you can try dropping D:\a\1\s\App\node_modules\@[REDACTED]\ui-tools\…

Can you check node_modules/typescript/package.json in your project? what’s version there?

Apologies for the delay. Since the time of my original question, we now have “~3.5.3” in our project’s package.json. The same version is also in node_modules/typescript/package.json that you asked be checked. The error is still visible in the build logs ##[error]ERROR: You are using version of Typ…

We are also seeing this in our Azure Pipelines build output. ERROR: You are using version of TypeScript 2.9.2 which is not supported; supported versions >=3.2.1 We are targeting ^3.0.0 in our project json and resolving to 3.7.3 in node_modules.

I can see from the logs it is picking up a version of typescript in a transitive dependency. Is there any way to correct this behaviour and use the top level typescript dependency?

@ojpbay , @brett.postin , Could you share full (debug, with -X option) logs? There is something fishy here, when analyzer is seeing old version of TS it should not even continue, I don’t get how you are getting any results. To get the version of TypeScript we rely on standard dependency resolution,…

@Lena the only relevant “typescript” logs I can see are the following: 2020-01-24T11:15:37.8032873Z 11:15:37.427 DEBUG: Looking for TypeScript recursively in D:\a\1\s 2020-01-24T11:15:37.8824610Z 11:15:37.880 INFO: Using TypeScript at: 'D:\a\1\s\App\node_modules\@[REDACTED]\ui-tools\node_modules' …

Hi Lena, I am seeing same error. It was working fine before. Error seems to be occurring after i have updated the plugin version for JavaScript. from 5.x to 6.x. ERROR: You are using version of TypeScript 2.6.2 which is not supported; supported versions >=3.2.1 ERROR: If it’s not possible to upgra…

Hi @upendar Which version of TS do you actually use? We had to bump the requirement for min TS version. So if you are using 2.6.2 it’s ok that after migration to 6.x analysis failed. If your project is using newer version and you have transitive dependency to 2.6.2. (like in the thread above), it s…

Can’t speak for others but we are currently using ~3.5.3. Look forward to the fix in the upcoming release! Many thanks.

Please ignore. I was using one of the old repos for my POC which had Type script V 2.6.2. I picked the latest one which is having “typescript”: “3.5.3”. this error is gone.

Error about unsupported TS version while project is using supported version

SonarQube Cloud

Lena (Elena Vilchik) Split this topic June 18, 2020, 7:33am 13

A post was split to a new topic: Global Typescript is used instead of local

Topic		Replies	Views
You are using version of TypeScript 3.1.6 which is not supported; supported versions >=3.2.1 SonarQube Cloud typescript , sonarqube-cloud	5	4463	October 23, 2019
Sonar 8.2 - wrong Typescript version found by Sonar SonarQube Server / Community Build typescript	2	1144	October 16, 2020
Global Typescript is used instead of local SonarQube Server / Community Build typescript , bug-no-category	7	1803	June 29, 2020
Typescript version issue SonarQube Server / Community Build typescript , sonarqube , azuredevops-server	1	733	August 4, 2021
*ERROR: Failure during analysis, Node.js command to start eslint-bridge was:" SonarQube Server / Community Build typescript , sonarqube	1	777	May 29, 2020

Error about unsupported TS version while project is using supported version

Related topics