-
Notifications
You must be signed in to change notification settings - Fork 32.3k
Stop recommending Vetur for Vue v3+ #143531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@zigomir thanks for filling this! Sorry but I do not use vue thus all the questions.... |
I see. I don't have the info, but if I had to guess, v2 is still used more than v3. About recommending Volar for Vue 2 (great question), it doesn't seem to be working out of the box based on the docs (look for Setup for Vue 2 details). I never used Volar and Vue 2 so am not best person to say. /cc @johnsoncodehk I guess I hoped VSC knows what version of Vue is being used, but if not, then maybe it's too soon to change this 🤷♂️ and am sorry to waste anyone's time 😊 |
Then I suggest that we only update this recommendation in the future once v3 becomes more popular than v2. I am open for suggestions from the community here. |
We have decided to start recommending Volar instead of Vetur starting in April for insiders. Which means May for VS Code stable. |
This has been done, and you can try it out with VS Code insiders from Thursday. Let's see how it goes. |
Since Vue.js version 3, new recommended extension has been Volar.
It would be great if VSCode could take this into account and stop recommending
Vetur
in Vue 3 projects.The text was updated successfully, but these errors were encountered: