VSCode not showing lint/syntax errors using Typescript

[jtsom]

• I have searched through existing issues
• I have read through docs
• I have read FAQ

Info

• Platform: MacOS
• Vetur version: 0.18.1
• VS Code version: Version 1.34.0-insider (1.34.0-insider)

Problem

When using Typescript in a Vue SFC app, if there are any lint problems or syntax errors (missing semi-colons, undeclared variables, etc), there is no indication in the editor of these errors. The only time it shows is when the application is build, then you have to parse through the error messages in the console.

Reproducible Case

Create new Vue app:
vue create new-app
choose Typescript and classes
open the project in VSCode. Make any changes that should trigger a red underline with errors / fixes. None show up, no fixes are available.

Line 38 should have a semi-colon at the end and there should be marked as a problem, but nothing is displayed.

Sort of invalidates the point of using Typescript and VSCode...

[octref]

@jtsom The temporary solution is #170 (comment)

If you have syntactical errors Vetur should report it. Can you upload your repro case to GitHub?

[jtsom]

As I mentioned in the report, to reproduce, all that is needed is a brand new Vue project. And change the one line that should report a message, with a possible fix-it:

Create new Vue app:
vue create new-app
choose Typescript and classes
open the project in VSCode. Make any changes that should trigger a red underline with errors / fixes. None show up, no fixes are available.