I have found this discussion: SonarCloud JavaScript Analysis Super Slow.
I have followed the workaround that it describes, aka creating a fake tsconfig.sonar.json
.
{
"include": [
"<same includes as for SonarCloud>"
],
"exclude": [
"<same excludes as for SonarCloud>"
],
"compilerOptions": { "allowJs": true, "noImplicitAny": true }
}
I have then configured SonarLint to use that file.
"sonarlint.analyzerProperties": {
"sonar.typescript.tsconfigPaths": "tsconfig.sonar.json"
},
This fixes the problem for SonarLint: it properly reports the problems in my VS Code without allocating more memory. I am now testing if the same solution also fixes the analysis of the app
folder on SonarCloud…