# Slow analysis of Javascript/Typescript

**URL:** <https://community.sonarsource.com/t/slow-analysis-of-javascript-typescript/94645>\
**Category:** SonarQube Cloud\
**Created:** [June 26, 2023, 9:43am UTC](https://community.sonarsource.com/t/slow-analysis-of-javascript-typescript/94645 "2023-06-26T09:43:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Raoul\_Blankestijn](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/raoul_blankestijn/32/46580_2.png) [@Raoul\_Blankestijn](https://community.sonarsource.com/u/Raoul_Blankestijn)\
**Post date:** [June 26, 2023, 9:43am UTC](https://community.sonarsource.com/t/slow-analysis-of-javascript-typescript/94645/1 "2023-06-26T09:43:06Z")

</div>

After: [Merge JS and TS analysis into single sensor · SonarSource/SonarJS@00b1ab0 · GitHub](https://github.com/SonarSource/SonarJS/commit/00b1ab0836d3362e2aa014ae9684c6ed63a07b29#diff-1526c3aaeed36a9a85353373f8272a98dd4c7dafa83801e21706f9e1eb0cc355)

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.

---

<div class="post-metadata">

**Author:** ![victor.diez](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/victor.diez/32/38525_2.png) [@victor.diez](https://community.sonarsource.com/u/victor.diez)\
**Post date:** [June 26, 2023, 9:51am UTC](https://community.sonarsource.com/t/slow-analysis-of-javascript-typescript/94645/2 "2023-06-26T09:51:12Z")

</div>

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](https://community.sonarsource.com/t/sonarcloud-scan-is-taking-very-long-time/94306):
>
> 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

---

<div class="post-metadata">

**Author:** ![Raoul\_Blankestijn](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/raoul_blankestijn/32/46580_2.png) [@Raoul\_Blankestijn](https://community.sonarsource.com/u/Raoul_Blankestijn)\
**Post date:** [June 26, 2023, 9:53am UTC](https://community.sonarsource.com/t/slow-analysis-of-javascript-typescript/94645/3 "2023-06-26T09:53:43Z")

</div>

Hi Victor,

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

Cheers to you as well,

Raoul