-
-
Notifications
You must be signed in to change notification settings - Fork 260
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
It appears that the Vetur config doesn't work well with Vetur v0.35.0? #595
Comments
I've filed a related bug in Vetur (as Github linked above), here: vuejs/vetur#3257 |
cc @xiaohulu |
Vetur doesn't seem to play well with typescript 4.5, see vuejs/vetur#3244 |
FWIW Vetur is no longer the officially supported IDE extension for Vue 3. Volar is officially recommended and works great w/ TypeScript as well. (I'm not affiliated in any way. I maintain vite-ts-tailwind-starter template and have been using both of these for a long time. Switched fully to Volar about a year ago, it's much better w/ Vue 3.) |
Thanks @Uninen,I will switch to Volar too. |
This is like a mistake in Vetur. For now, I'll close it. |
Describe the bug
First: Why I'm filing this bug here. As a new-to-Vue user, I wasn't sure what in the world was going on here. I was unfamiliar with Vetur and I had to spend some time debugging the issue. While it's arguable that this is a problem with Vetur, it's definitely a distraction from getting started with Vue-in-electron fun, and I think it would be a good idea for this project to shield new users from errors unrelated to the content of the project. I think I'd recommend commenting out that line in the vetur config. (It might even be nice for new users if there was some comment documenting what in the world the Vetur config is, and/or what they should know about it)
With a fresh clone of this repo, using the latest VS Code and the latest Vetur extension (at the time of the writing). I'm getting a TON of errors (aka "red squigglies") until I disable the experimental template interpolation.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No errors in the IDE.
Screenshots
Additional context
Workaround
For now, simply commenting out
'vetur.experimental.templateInterpolationService': true
and running the VS Code commandVetur: Restart VLS
will resolve the issue. However, I don't get types in the template.The text was updated successfully, but these errors were encountered: