Corrupted errors in TypeScript files

[tills13]

• VSCode Version: 1.17
• OS Version: macOS Sierra 10.12.6

Steps to Reproduce:

1. Create a .ts/x file

I can't figure out how to capture the popups without them closing - but, In the above example above:

• the error on import is

[ts]
Cannot find name 'import
'.

(note the newline)

• the errors on line 18 are

[ts] Cannot find name 'con '.
and
[ts] Cannot find name 'icon '.

etc...

If I add lines above, the errors stay in place (character count wise). i.e. if I were to add let x = 1 after const mClassName... the errors would offset 9 characters (flowing up lines if necessary).

Reproduces without extensions: Yes

[tills13]

I disagree with the "New Release" label - I've had this happen to me on a couple versions of VSCode over the last couple months.

Also, further information - I've had this happen on all three major platforms (Windows 10, Ubuntu 16.04, and macOS Sierra).

[mjbvz]

I've seen similar problems. The root cause for me seemed to be microsoft/TypeScript#16540

@tills13 If you're able to reliably reproduce this, can you please try installing typescript@next in your workspace and enabling it to see if the problem has been resolved upstream

[tills13]

I played around with TS 2.6.0-dev.20171012 a little bit today and it seems to have fixed it. I will keep my eye on it over the next couple days and post here if I run into anything (or if I don't)

[mjbvz]

Closing this as one of the possible root causes was addressed by TS 2.6. Please let me know if you start seeing this issue again