-
Notifications
You must be signed in to change notification settings - Fork 53
ERROR: Failed to find a source file matching path <path> in program created with <path_to_tsconfig> #786
Comments
Additional info:
Is there something wrong with this? |
Hi @venttola, Please, try to change I suspect it's because of |
That seemed to do trick, thanks for the help! I'm using Gulp for building, and I guess is somehow overrided the faulty value in tsconfig.json. I checked my other project's tsconfig.json and there the outDir option is a lot more sensible. Just the confirm: This was a TypeScript compiler issue, which the plugin internally uses? If this is the case, could it be mentioned in a little bit more clear way in the documentation of SonarTS -plugin? |
Context: Sonarcloud unable to detect declaration files. Reference: SonarSource/SonarTS#786
I'm getting same issue with react & typescript project. Is there any solution for this? my sonar props and tsconfig.json is |
I am getting the same errors in my Angular 9 project. Is there any solution? Here is my tsconfig.app.json {
"extends": "./tsconfig.base.json",
"compilerOptions": {
"outDir": "./out-tsc/app",
"types": []
},
"files": [
"src/main.ts",
"src/polyfills.ts"
],
"include": [
"src/**/*.d.ts"
]
} |
hello @sivantha96 , can you please post your problem on our community forum https://community.sonarsource.com/ ? |
I want to report a bug.
SonarTS version: 5.0
Node.js version: 11.6.0
TypeScript version: 2.8.3
SonarQube version: 7.4
Reproducer
Logs
Expected behavior
Analysis should succeed.
I was able to analyze my project once, but then all of a sudden it did no longer find my source files. No analysis for my source files is found at my SonarQube instance.
Analysis in the same environment for other Typescript projects works without any issues.
The text was updated successfully, but these errors were encountered: