TS2304 Errors appear for excluded files in Visual Studio 2017

[RobertoPrevato]

Hi,
Premise: I looked carefully for existing issues but didn't find a working answer (although I found many speaking about the same topic).

I am working with Visual Studio 2017, on an ASP.NET MVC Core application where the front end will be implemented using React, ES6 and Babel. No TypeScript.
I have a node_modules folder, hidden in FS and excluded from project, which contains some source .ts files from an external library (react-router).

When I open the solution, after few minutes 4 errors appear as compilation error (TS2304 Cannot find name 'object')

What I tried to do:

1. Add following configuration to inside .csproj file + Close and Reopen solution

<TypeScriptCompileBlocked>true</TypeScriptCompileBlocked>

2. Disable JavaScript/TypeScript new service + Close and Reopen solution
   

But this wasn't sufficient. To resolve, I needed to disable the TypeScript extension completely from VS and close every instance of VS 2017.

3. Disable TypeScript extension
   

Which in turn removed completely the "JavaScript/TypeScript" entry from Options / Text Editor settings.

Expected behavior:
TS2304 Errors should not appear for files that are not included in the project. In the same way as C# files that are not included in the project (or are not set to "Compile" build action) do not affect compilation (for example). This should not require any special action.

Actual behavior:
Behavior of TypeScript files is inconsistent with other programming languages used in VS. Compilation errors such as TS2304 are appearing also for files that are excluded from project and even hidden in file system.

---

Kind Regards,
Roberto

[mhegazy]

Are you seeing this on 15.2?

[RobertoPrevato]

Hi @mhegazy, thanks for answering. No, I didn't update today my VS - I will update tomorrow at work and let you know.

[RobertoPrevato]

Hello again, @mhegazy. After updating to latest version 15.2, the issue I described went away. Thank You!

[guylando]

Please reopen this issue.
This issue still occurs for me in visual studio 15.3 with following excludes I still get errors from ts files from a subdirectory of lib:

"**/wwwroot/lib/*", // Don't operate on lib directory to prevent warnings from lib code
  "wwwroot/lib/*", // Don't operate on lib directory to prevent warnings from lib code
  "wwwroot/lib", // Don't operate on lib directory to prevent warnings from lib code
  "wwwroot/lib/**", // Don't operate on lib directory to prevent warnings from lib code
  "**/wwwroot/lib/**", // Don't operate on lib directory to prevent warnings from lib code
  "wwwroot/lib/" // Don't operate on lib directory to prevent warnings from lib code

[RobertoPrevato]

Hi,
I am reopening the issue because of two reasons:

• others are saying this exact problem came back with VS 15.3
• since a few weeks, Visual Studio became really slow when compiling of a solution which contains a node_modules folder (the same project I was referring to when first opening this issue)

Note that I have TypeScript extensions completely disabled; the node_modules folder is hidden in the file system and excluded from the project. Nevertheless, the compilation is impacted by the presence of this folder. The situation is even worse than it used to be, since even having TypeScript extensions disabled doesn't help. I understand this is not exactly the same problem, but I think it may be related.

[mhegazy]

//cc @billti, @amcasey

[jfrank14]

I have VS 2017 v15.4.5 and have this problem as well. Since my project uses Typescript heavily, this is blocking my ability to upgrade to VS2017 at all.

[shakazulu89]

anyone had any luck with this?

[jfrank14]

Not really. I have worked around this by deleting the node_modules/@types directory, and then the errors go away. But I have to do this frequently, because npm recreates the folder. This works but it's very annoying.

[RobertoPrevato]

My recommendation is to keep your client side ES6/TypeScript source code in a completely different folder than the one used by your server side code and Visual Studio, and configure the build tasks to deploy client side build artifacts into the wwwroot folder of the ASP.NET Core application. I did this in the last web application I am working on. It's annoying but it solves the problem with VS.

[rastislavbodorik]

Same issue has start form me after I have update Visual Studio 2017 to 15.5.0, versions 15.5.1 and 15.5.2 does not solve this, I have installed Typescript 2.6.2 for Visual Studio 2017. Typescript is compiling *.config files, so there are thousand of typescript errors.

[typescript-bot]

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.