Slow analysis of Javascript/Typescript

[Raoul_Blankestijn]

After: Merge JS and TS analysis into single sensor · SonarSource/SonarJS@00b1ab0 · GitHub

The analysis of our TypeScript code began very slow. Almost twice as long as it used to. Could you please offer a solution for this? It now costs more than 16minutes extra to build our FE application.

[victor.diez]

Hi @Raoul_Blankestijn,

Thanks for the feedback. Yes we are aware of this issue since last release. Please check this post for the workaround until we do a fix:

SonarCloud scan is taking very long time

ALM used - GitHub CI system used - GH actions Languages of the repository - ts We have sonarCloud configured for our nx monorepo (sonar.typescript.tsconfigPath is pointing to tsconfig in the monorepo root) We trigger the scan via our GitHub actions workflow using the action: SonarSource/sonarcloud-github-action@master. Until a few days ago our setup was working as expected, we are now experiencing a huge performance degradation: scans on PR (one line modified) takes hrs - the scan tries to…

In principle, using the property sonar.typescript.tsconfigPath to point to the tsconfig.json in the project root should solve the issue.

Cheers,
Victor

[Raoul_Blankestijn]

Hi Victor,

Thanks for your quick response! We will try the workaround.

Cheers to you as well,

Raoul