This project is read-only.


Falsy errors with


I'm on VS2013 and I'm getting this problem but it also appeared in 2012, which is current with other people here:

Basically, when a file that a lot of other files depend on is temporarily broken with a syntax error, the error is propagated to the other files but the when the error is fixed, the syntax errors don't disappear from the dependent files.

However, building the project succeeds (errors remain in error list window) and closing and reopening the dependent files seems to fix the issue when it occurs.

A very rough repro - I'm saying rough because I don't know if it happens every time or under some conditions:
  • Have file A.ts
  • Have file B.ts that depends on definitions from A.ts
  • Break something in A.ts and save (not sure if save is important)
  • Error list will be populated with errors in both A and B
  • Fix error in A
  • Error list remains populated with errors from B
  • Building the project will succeed
PS: I thought this was due to Web Essentials but still occurs with Web Essentials disabled, though less often.
Closed Nov 20, 2013 at 10:58 PM by danquirk


RyanCavanaugh wrote Oct 11, 2013 at 10:14 PM

I can't reproduce any problems with the repro steps listed - tried introducing all sorts of different errors and didn't see anything weird. If you run into something specific, please reopen and I can try again.

One problem you might be seeing is a design limitation in v1 where errors produced by the 'build' step are not properly merged with errors produced by the language service itself. In other words, you might see an stale error form the build appearing as if it were real. Rebuilding should make those stale errors go away. If you see something inconsistent with that scenario please reopen. Thanks!

** Closed by RyanCavanaugh 10/11/2013 2:14PM

georgiosd wrote Oct 30, 2013 at 10:10 AM

I can't find a way to consistently reproduce this but it's definitely there.

See this one for example:

This was after opening the file fresh and editing some lines above it.
The "module" keyword was never touched and yet I get a "dule" does not exist on type.
If I compile it compiles fine though so it must be something fishy with the language service.

Do you guys have any way to enable comprehensive debug output for the language service in case we can trace the problem?

danquirk wrote Nov 7, 2013 at 7:48 PM

We're looking into getting something to give you to help track this down. We'll keep you posted.

RyanCavanaugh wrote Nov 19, 2013 at 7:52 PM

Can you try with the 0.9.5 beta and let us know your results?


georgiosd wrote Nov 20, 2013 at 10:21 AM

Just installed it - will let you know if it comes up again.

danquirk wrote Nov 20, 2013 at 10:58 PM

Closing for tracking purposes, please do re-open if you see anything strange like this with 0.9.5 and we'll get on it.

georgiosd wrote Nov 27, 2013 at 9:18 AM

Worked a whole day with it yesterday and it didn't come up. I'll also consider it fixed and let you know if I find it otherwise.

Out of curiosity, what was the problem?