It appears that the Vetur config doesn't work well with Vetur v0.35.0?

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:

1. clone the repo
2. npm install
3. Open in VS code with the latest Vetur installed (v0.35.0)

Expected behavior No errors in the IDE.

Screenshots

Additional context

• OS: Windows 10
• VS Code:
  • Version: 1.62.3 (user setup)
  • Commit: ccbaa2d27e38e5afa3e5c21c1c7bef4657064247
  • Date: 2021-11-17T08:11:14.551Z
  • Electron: 13.5.2
  • Chrome: 91.0.4472.164
  • Node.js: 14.16.0
  • V8: 9.1.269.39-electron.0
  • OS: Windows_NT x64 10.0.19042
• Vetur Extension version 0.35.0

Workaround

For now, simply commenting out 'vetur.experimental.templateInterpolationService': true and running the VS Code command Vetur: Restart VLS will resolve the issue. However, I don’t get types in the template.

[Peeterush]

Vetur doesn’t seem to play well with typescript 4.5, see vuejs/vetur#3244

[cawa-93]

This is like a mistake in Vetur. For now, I’ll close it.