Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

VisualStudio Code shows errors in new project

See original GitHub issue

Version

3.0.0-beta.6

Reproduction link

https://github.com/xcambar/vue-cli-lint-error-typescript

Steps to reproduce

vue create name-of-your-project
Select only the “TypeScript” option
open HelloWorld.vue in VSCode

What is expected?

The linter service and VSCode should provide the same amount of feedback to the user.

What is actually happening?

The linter service does not throw any error, but VSCode does.

I’m new to vue-cli, and despite my Google-fu, I may have missed something.

Issue Analytics

State:
Created 5 years ago
Comments:5 (1 by maintainers)

Top GitHub Comments

1reaction

xcambarcommented, May 11, 2018

I confirm the fix described in https://github.com/vuejs/vetur/issues/682#issuecomment-364267867 works, thanks @kumorig !

It will do before Vetur 0.11.8 is published 👍

1reaction

kumorigcommented, May 11, 2018

I can confirm this issue, and I’m pretty sure it has to do with the typescript version. The vetur-extension in vscode installs with devDependencies:{"typescript": "^2.6.2"} (looking at %USERPROFILE%\.vscode\extensions\octref.vetur-0.11.7\package.json ) but https://github.com/vuejs/vetur/blob/master/package.json has "typescript": "^2.8.1", but vetur@0.11.7 is the same version so whats up with that?

Anyway, definite assignment assertions (the exclamation marks after variables), where your code breaks the linter, were introduced in typescript v2.7