VTI feedback thread

VTI (Vetur Terminal Interface) is available since 0.23.0.

Docs: https://vuejs.github.io/vetur/vti.html

Usage:

npm i -g vti
# run this in the root of a Vue project
vti
vti diagnostics

It’s not very well tested. I don’t have the bandwidth to test it in real world projects.

Formatting can be done, but I’m not sure what config to prefer.

Anyway, this surfaces Vetur’s interpolation service’s errors onto CLI. When this becomes stable enough, it can help people catch errors currently uncatchable by Vue’s compiler or Webpack.

If you have bug with repro cases, open new issues.

[yoyo930021]

@P4sca1 @lzxb Follow #2449

[Popeye4242]

I don’t know if vti is still relevant but from my experience its setup is too hard to be worth it.

'this' implicitly has type 'any' because it does not have a type annotation. Cannot find name '__vlsComponentData'. Cannot find name '__vlsComponentHelper'.

This are issues that every single user would face but it is not documented how to resolve them. So vetur is useless as its just highlighting every single line in vue files.