Vetur: Fear upgrading

Created on 9 Dec 2020  路  6Comments  路  Source: vuejs/vetur

Whenever I dare clicking the update button for this extension, or Prettier or Eslint, something for sure will break. So good the vsix file is there.
I didn't want a jsconfig.json file, don't need it, but I added it just for Vetur. Still formatting is not working anymore. I get error in status bar Extension Vetur cannot format... file name. Was working just fine in previous version.

I just wish when publishing an update you would deal with backward compatibility and migrate settings automatically.

question

Most helpful comment

I didn't want a jsconfig.json file,too

All 6 comments

I didn't want a jsconfig.json file,too

The format problem is fixed.
I will release new version tonight.

The jsconfig.json is only a warning.
If you don't need to talk vetur any speical option, you can ignore it.
You can use vetur.ignoreProjectWarning: true in vscode setting to close this warning.

https://vuejs.github.io/vetur/guide/FAQ.html#vetur-can-t-find-tsconfig-json-jsconfig-json-in-xxxx-xxxxxx

The format problem is fixed.
I will release new version tonight.

The jsconfig.json is only a warning.
If you don't need to talk vetur any speical option, you can ignore it.
You can use vetur.ignoreProjectWarning: false in vscode setting to close this warning.

vetur.ignoreProjectWarning: true

All instructions are here.
https://vuejs.github.io/vetur/guide/FAQ.html#vetur-can-t-find-tsconfig-json-jsconfig-json-in-xxxx-xxxxxx

thank you

I have no intention of changing people's habits.
But we get too many questions about the config file.
These warnings are intended to alert users to possible problems.

Was this page helpful?
0 / 5 - 0 ratings