In my Visual Studio Typescript project, I am in the process of transforming a large library of legacy JavaScript files by renaming them to *.ts and adding type information to enhance application safety. With over 200 files to modify, it's quite a task.
Currently, I have a tsconfig file set up with specific compiler options tailored to my needs:
{
"compileOnSave": true,
"compilerOptions": {
"target": "es5",
"module": "ES6",
"allowJs": false,
"lib": [ "dom", "es5", "scripthost", "es2015.promise", "es2016.array.include" ]
},
"include": [ "**/*"]
}
While Visual Studio is able to scan open ts files for compilation errors and display them in the Error List window, it falls short when it comes to scanning files that are not currently open in the IDE. This means I have to manually open each file to detect errors, which is time-consuming and cumbersome for a project of this magnitude.
The primary goal of incorporating TypeScript into my workflow is to ensure that the entire code base is under constant scrutiny during compilation. I want to be alerted immediately if an error is introduced due to changes like deleting a variable. However, the manual checking process inhibits this objective.
I am looking for a solution that enables Visual Studio to comprehensively scan the entire project and aggregate a list of all errors across all files, regardless of whether they are currently open or not. Any suggestions on how to achieve this would be greatly appreciated.