Vue author You Yuxi published an article looking forward to 2023 and looking back at 2022!

Vue author You Yuxi recently published an article reviewing Vue’s 2022 and looking forward to the project’s development in 2023.

The following is the original content of You Yuxi (translation):

Looking back on 2022

2022 2 In March, we switched the default version of Vue to 3.x. This transition marks the readiness of all official parts of the v3 framework, including significant revisions to the documentation that provides the latest best practice guidance.

We are still in the transition period of the ecosystem migrating to Vue 3. Therefore, following the switch, we are more focused on improving the developer experience with Vue by investing in tools. Our team members have been actively involved in the development of Vite, and we made significant improvements to Vue’s IDE and TypeScript support with the release of Volar 1.0.

During 2022, we saw NPM usage of Vue 3 grow by nearly 200%. On the community side, the Vue 3 ecosystem is now mature and offers great solutions that help increase productivity. Nuxt 3 and Vuetify 3 both reached stable status in November 2022, and NativeScript for Vue 3 recently launched in beta. Additionally, we’d like to give a shout-out to the other great projects that have been supporting Vue 3 for a long time: Quasar, NaiveUI, Ionic Vue, PrimeVue, InkLine, ElementPlus, and others.

Although Vue 3 is now the default, we know that many users have to continue using Vue 2 due to migration costs. To ensure that Vue 2 users benefit from the framework’s advancements, we decided to move Vue 2’s source code to TypeScript and backported some of the most important Vue 3 features in Vue 2.7. We've also ensured that Vite, Vue Devtools, and Volar all support both Vue 2 and Vue 3.

What will happen in 2023?

Smaller and more frequent minor versions

With the release of the last Vue 2 minor version (2.7), we expect it to be released in 2023 Vue 3 core features will be launched at full speed this year. We have a long feature list and we're excited to keep working on it!

One thing we want to improve is our release cadence. Vue follows semver, which means we should only release minor version features. In the past, we took a "big minor" approach, where we combined many features into large, infrequent minor releases. This results in quite a bit of low-complexity functionality being blocked while we work on other high-complexity functionality. In 2023, we hope to release smaller, more frequent minor releases so we can roll out more features faster.

This also means we will be adjusting things in 3.3. Originally, we planned to graduate Suspense and Reactivity Transform from experimental status in 3.3. However, we believe both still require further RFC discussion, and they should not prevent other more straightforward features from being implemented. Now, the goal for 3.3 is to get proposed/planned features that are clear winners and don't require RFC discussion - for example, support for external import types in the

In the meantime, we will:

• Further evaluate readiness for Suspense and Reactivity Transform.

• Take the time to evaluate outstanding user-submitted RFCs and feature requests.

• Publish RFCs for features we intend to implement in 3.4 and later, such as SSR lazy hydration.

Look forward to more details later this month.

Another thing to note is that there are no major breaking changes planned for the foreseeable future. Recognizing the challenges users faced during the transition from v2 to v3, we want Vue to have a better long-term upgrade story.

Vapor Mode

Vapor Mode is another compilation strategy we have been experimenting with, inspired by Solid. Given the same Vue SFC, Vapor Mode compiles it into JavaScript output that is more performant, uses less memory, and requires less runtime support code than the current virtual DOM-based output.

It’s still early days for Vapor Mode, but here are some high-level takeaways:

• Vapor Mode is suitable for use cases where performance is the primary concern. It is opt-in and will not impact existing code bases.

• At the very least, you will be able to embed a Vapor component subtree into any existing Vue 3 application. Ideally, we'd like to implement granular opt-in at the component level, which means freely mixing Vapor and non-Vapor components in the same application.

• Building an application using only Vapor components allows you to remove the virtual DOM runtime from the bundle, thereby significantly reducing the baseline runtime size.

• For best performance, Vapor mode will only support a subset of Vue features. In particular, Vapor Mode components will only support the Composition API and

We will share more details as we make more progress later this year.

For more details, please see the original English text: https://blog.vuejs.org/posts/2022-year-in-review.html

Related recommendations: 《 Take on private jobs and make money! A complete list of order-taking platforms for programmers in 2023! 》