Dropping Vue 2 and vue-class-component Support in v3.1

[johnsoncodehk]

We're announcing the upcoming removal of Vue 2 and vue-class-component support from our packages and VSCode extension.

Timeline

• March 2023: vue-class-component was officially deprecated
• December 2023: Vue 2 reached EOL
• Upcoming 3.0 release: This will be the last version with Vue 2 support
• October 2025 (planned 3.1 release): Vue 2 support will be completely dropped

Reasons for This Change

1. Maintenance Burden: Supporting legacy Vue 2 and vue-class-component significantly increases code complexity and maintenance effort
2. Contribution Barrier: The additional compatibility layer makes it harder for new contributors to participate
3. Ecosystem Alignment: The Vue ecosystem has largely moved to Vue 3 and Composition API

What This Means

• After 3.0, we will no longer address Vue 2-related issues in our language tools
• New features will be Vue 3-focused
• The codebase will be simplified to improve maintainability

For Vue 2 Users

If you still need to work with Vue 2 projects:

• You can pin your extension version to 3.0.x
• Critical bug fixes will still be backported to the 3.0.x branch

We encourage all users to migrate to Vue 3 if possible. This change will allow us to focus our efforts on improving the Vue 3 experience and modern features.

Thank you for your understanding and support!

[iulo]

Could you create a legacy version of the vscode extension? Like "Vue Legacy (Official)".
We maintain both Vue2 and Vue3 projects, and using project workspace settings to limit which extension to use will make it easier to use.

[empresarrollo]

We are in the same boat. We have a couple of big legacy vue 2 apps, it would be great to have a "vue legacy" extension

[nateainsworth]

I've always been keen to take on the task of updating a large Vue 2 project migration to Vue 3. I would be up for it if anyone's open to hiring. I've done a fair bit of dabbling in it in the past. From my experience, the issue is mainly the other Vue libraries, which must be converted simultaneously. The best I've got on my CV is a 500-component strong rebrand, so a large migration would be right up my street. But i agree a legacy version would be handy just to avoid breaking changes in the future if your focus is off Vue2. Just like the Chrome extension legacy version.

[YFengFly]

Strongly agree! I also have multiple projects using both Vue 2 and 3. Extensions like "Vue Legacy (Official)" could clearly state from the start that they are a fork of the "Vue(official) 3.0" package, providing only essential bug fixes and maintained until a specific end date (e.g., XX year XX month).

Ideally, this could be handled automatically—such as reading the Vue version from package.json to switch extension features accordingly. Even manual switching would be acceptable; users could be advised in the extension’s description to disable the extension for specific projects via the "Disable (Workspace)" option in the extensions panel. This is far more convenient than constantly upgrading or downgrading manually.

This approach allows new Vue 3 projects to take advantage of the latest extension features, while still supporting older Vue 2 projects seamlessly.

[ngyyuusora]

useful idea! vue2.7 existed using there, hope it!

[gnpwaritschlager]

The current extension code doesn't go away though, does it? So can't you just install the pre-3.1-version .vsix extension bundle manually and disable updates?

[Glandos]

Thanks for maintaining Vue2 support for so long, and especially in this new version.

I'm also maintainer for a Vue2 app which is very complicated to migrate to Vue3 (it's very big), so we'll definitely need Vue2 support for at least 2 more years.

We are using composition and script setup, but then we'll have to move to Vuetify3 + Vue3 all at once, and that's a very high step.

[abea]

For what it's worth, I upgraded our 600+ component code base in a few months (webpack → Vite, Vuetify, and Vue) a couple of years ago. That was in parallel with continued feature work. It's not a small project, but the component changes are much less than I had expected. The Vue 3 upgrade guide and Vuetify upgrade guide made things pretty clear. The vue 3 linter config (vue3-strongly-recommended) and Vuetify linter config (eslint-plugin-vuetify) took care of most of the little changes automatically (always double-check it) and made the rest easy to see. That's just to say that it's not only worth prioritizing, but might not be the blocker that it seems from the start.

[towry]

Not good news for Vue2 users.

[vishwanathan3109]

As a vue3 option and composition developer, it may be very useful update for me although i wont use vue2 much, but it may save me some time from thinking the bugs related to the versions

[NotTsunami]

We have a legacy Vue 2 + Vuetify 2 project as well. I was able to migrate it all the way to Vite 6 to at least cover some of the transition, but that's the last version that is compatible with Vuetify 2 due to sass being restricted to 1.32.13. As a note for anyone attempting to use Vite 6 with that configuration needs to add this to their vite.config.js:
css: { preprocessorOptions: { sass: { api: 'legacy' } } },
We are also using Vee-Validate, Vuex and Vue-Router, which would also need to be upgraded to their Vue 3 versions, which is outside of the scope of the mentioned project at this time, so I hope some sort of legacy option can be maintained.