Hi. Sorry but I don’t really know what is the workaround. Like should I switch to GitHub Actions to call sonarcloudn or? tsconfig is there in the repo, and proper dev dependency is also available
There is a tsconfig in the repo… which is extending from another tsconfig file that’s only available once an npm install is run.
{
"extends": "@sindresorhus/tsconfig",
....
SonarCloud will not run this npm install for you when using Automatic Analysis, so witching to GitHub actions (where SonarCloud analysis is run after you’ve fetched all the dependencies) is probably the best option.