Project Status

[yoyo930021]

Hi everyone, I'm the main maintainer in Vetur now.

As you can see, the project has not been updated for a long time.
There are many people who are concerned about the future of this project.

I will go back this September.

Here are the future plans:

• v0.37.0 (Now here)
  • Basic Support Vue 2.7 LTS
  • Fix many serious bugs
    • Type-checking broken with TypeScript 4.5.x+ #3323 VTI not compatible with Typescript 4.6.4. #3424
    • VUE Language Server crashed 5 times in the last 3 minutes #3520
    • more
• Announced to enter LTS status.
  • Only fix serious bugs.
  • Not add any new features.
  • Add some vetur feature to volar for help user migrate to volar.
  • End of Life by the end of 2023 (Same as Vue 2.7)
    • https://blog.vuejs.org/posts/vue-2-7-naruto.html
• Transferring development energy to volar

We would like to thank everyone for their support over the years. Due to time constraints, we hope contributors can focus on maintaining single editor support.
Thank you to the contributors, especially @octref @rchl @HerringtonDarkholme @ktsn.
Without @octref and @HerringtonDarkholme, this project wouldn't be possible
@ktsn contribute template type check. @rchl reviews some important PRs.

Thanks @johnsoncodehk, volar is a great project for improving Vue developer life.

[KujoMiva]

I like the code formatting function of vetur very much.

[mariomuvambo]

ajudou bastante. obrigado!

[liangzhenrong1]

为什么模板代码高亮变灰了，而注释的高亮颜色也没了
Why does the highlighted template code turn gray, and the highlighted color of comments also disappear

[yoyo930021]

为什么模板代码高亮变灰了，而注释的高亮颜色也没了 Why does the highlighted template code turn gray, and the highlighted color of comments also disappear

It is a upstream bug, try to downgrade typescript version.
If have any question, please open a new issue.

[Skriptach]

1. Autocomplete stop working
2. Alt + click on a component use in a template stop open that component in a new tab

[stefnotch]

Should the Visual Studio Code documentation also be updated to reflect on this?
https://code.visualstudio.com/docs/nodejs/vuejs-tutorial

[harvey-woo]

In my current situation, I can only turn off eslint-plugin-prettier for vue files and use all eslint rules.
For vscode, turn off editor.codeActionsOnSave["source.fixAll.eslint"] globally and open it for vue files

.vscode/settings.json

     "editor.codeActionsOnSave": {
        "source.fixAll.eslint": false
     },
     "[vue]": {
         "editor.codeActionsOnSave": {
            "source.fixAll.eslint": true
         },
     }

.eslintrc.js

module.exports = {
    // for vue files
    ...globalConfig,
    
    overrides: [
        files: ['!*.vue'],
        extends: [
            'plugin:prettier/recommended',
        ],
        'prettier/prettier': [
            'error',
            {
              singleQuote: true,
              parser: 'flow',
            },
          ],
    ]
}

[Lehoczky]

Now that Vue2 reached it's EoL, I think it would be a good step to deprecate the Vetur VSCode extension in favour of Volar (recently renamed to Vue - Official). Searching for Vue plugins in the marketplace still ranks Vetur higher than Volar due it having twice as many downloads.

An extension can be marked as deprecated by reaching out to the VSCode team in this discussion: microsoft/vscode-discussions#1

[xak2000]

deprecate the Vetur VSCode extension in favour of Volar

As I see in the linked discussion the Volar is deprecated in favor of the Vue - Official extension. Moreover, I cannot even install Volar now due to its deprecated status.

I'm confused. Is Vetur deprecated in favour of Volar and Volar is deprecated in favor of Vue - Official? It doesn't make sense to me. What extension should I use today to develop Vue3 apps with TypeScript?