vetur VS vscode-runonsave

If you use the Vetur extension for Vue language features, you are out of luck. There is a long-standing request for adding this behaviour to Vetur.

The first step is to enable the Volar extension and disable the Vetur extension. Volar is the new recommended extension to use with Vue 3 and typescript.

Volar is supposed to be the upcoming replacement for Vetur, the Vue.js lsp server. It looks like it's significantly better than Vetur; has anyone tried it in lsp-mode in emacs?

There is a known bug in Vetur, the Vue VSCode extension, where it takes forever (sometimes several minutes!) to lint Vue files on save.

Now, we can create regular ol' Vue SFCs, or single file components. By creating the whole component in one file, we get the flexibility of thinking of our components as one functional unit made up of HTML, JavaScript, and CSS. We can also write components in TypeScript or SASS if we want to. We can also get syntax highlighting since SFCs end up being fundamentally HTML documents. And with VSCode plugins like (Vetur)[https://vuejs.github.io/vetur/], development in SFCs has a lot of benefits going for it.

You didn’t give much info, but from what I can tell from your screenshot you are writing in Vue and therefore are probably using Vetur. In that case the only info I could find was an issue from 4 years ago that seems to say you should just turn off style validation.

Vetur - Vue tooling for VS Code

The details are that the Node command is actually a command that is run by a VSCode extension: [Run on Save](https://github.com/emeraldwalk/vscode-runonsave)..) I've posted this issue there, but there has been no reply. The Run on Save settings in this case are:

Luckily there is a very easy workaround where, instead of asking Vetur to use Eslint to lint the file on save, we could do it ourself using the RunOnSave VSCode extension.