在 Visual Studio 中将打字稿错误报告为警告，并且不会使构建失败

Question

I want to typecheck existing javascript code. To that end, I have specified the following tsconfig. Running tsc results in a couple of hundred errors, which show up in Visual Studio when I do a build. However those errors now also fail the build. As the code is currently functioning, I want to postpone resolving those errors. I want the errors to be reported as warnings, such that the build will continue and we can gradually improve the javascript.

// tsconfig.json
{
  "compilerOptions": {
    "noImplicitAny": false,
    "noEmitOnError": true,
    "removeComments": false,
    "sourceMap": true,
    "target": "es5",
    "checkJs": true,
    "allowJs": true,
    "noEmit": true
  }
}

//csproj (abbreviated)
<Project>
  <Import Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)\TypeScript\Microsoft.TypeScript.Default.props" Condition="Exists('$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)\TypeScript\Microsoft.TypeScript.Default.props')" />
  <PropertyGroup>
    <TypeScriptToolsVersion>3.6</TypeScriptToolsVersion>
  </PropertyGroup>
  <Import Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)\TypeScript\Microsoft.TypeScript.targets" Condition="Exists('$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)\TypeScript\Microsoft.TypeScript.targets')" />
</Project>
...

Example msbuild output:

...
file.js:153:33 - error TS2769: No overload matches this call.
========== Build: 14 succeeded, 1 failed, 23 up-to-date, 0 skipped ==========

Answer 1

As far as I recall, msbuild's exec command searches the output for the word error , and if found will emit a build error.

Which it seems that this linter *.targets file is doing. And seems to be corroborated here:
Does the MSBuild Exec task search STDOUT for the string "error"?

But really:
If you want to postpone fixing those errors, I see no choice but to simply rip out your linter from your *.csproj files completely. I mean why put in the linter only to ignore it and defer your technical debt?

In that case I'd simply put take that code you shared, and pull it out of the .csproj file and put it into a separate, standalone msbuild file and run it separately.