-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VisualStudio Code shows errors in new project #1261
Comments
#1198 ? |
Unfortunately no (or I don't understand the solution): the example repo already contains the declarations as 2 separated files |
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 Anyway, definite assignment assertions (the exclamation marks after variables), where your code breaks the linter, were introduced in typescript v2.7 |
Workaround here: vuejs/vetur#682 |
I confirm the fix described in vuejs/vetur#682 (comment) works, thanks @kumorig ! It will do before Vetur 0.11.8 is published 👍 |
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
HelloWorld.vue
in VSCodeWhat 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.
The text was updated successfully, but these errors were encountered: