I am currently working on an asp.net core 2.2 project that is running on .net 4.7.2. This project includes the Microsoft.TypeScript.MSBuild nuget package.
Each time I introduce a new typescript (.ts or .tsx) file to my project, Visual Studio automatically inserts:
<ItemGroup><TypeScriptCompile Remove="myFile.ts" /></ItemGroup>
line into my project's .csproj file.
The tsconfig file for my project is as follows:
{
"compilerOptions": {
// Target latest version of ECMAScript.
"target": "esnext",
// Search under node_modules for non-relative imports.
"moduleResolution": "node",
// Process & infer types from .js files.
"allowJs": false,
"jsx": "react",
// Don't emit; allow Babel to transform files.
"noEmit": true,
// Enable strictest settings like strictNullChecks & noImplicitAny.
"strict": true,
// Disallow features that require cross-file information for emit.
"isolatedModules": true,
// Import non-ES modules as default imports.
"esModuleInterop": true,
"skipLibCheck": true,
"baseUrl": ".",
"paths": {
/* my paths */
}
},
"include": [
/* my typescript folders */
],
"exclude": [ "node_modules" ]
}
It is worth noting that I am only utilizing the package for type-checking purposes, while the actual compilation is managed by Babel.
I am seeking assistance in comprehending the reason behind Visual studio's addition of these TypeScriptCompile Remove lines in my project. Is there a mistake on my end?