It was a moment of celebration across the Vueniverse. At last, after more than a year of Vue 3 being available on the next
branch of all the core repositories (and many of the related frameworks and libraries), Vue 3 has been officially released to the world as the recommended way to write Vue applications. The moment was noted on the official Vue blog as well as on Twitter.
🎉 It’s done! Vue 3 is now the default version and the brand new https://t.co/0N2uGPCtsh is live!
— Vue.js (@vuejs) February 7, 2022
More details in the blog post in case you missed it: https://t.co/ub8L4KhPsJ
Considering that the initial release of Vue 3 (named “One Piece”) was originally released on September 18, 2020, the fact that we’re only now reaching the official recommendation has shaped the Vue ecosystem. For applications, most of the actual migration between Vue 2 to Vue 3 is straightforward, with Vue minimizing breaking changes while adding new features such as the Composition API as well as the latest new feature to land in Vue, <script setup>
, which provides a way to build Vue apps without so much boilerplate code (I presented a demo of using Composition API and <script setup>
alongside Ben Hong at VueJS Athens, check it out!).
However, the Vue ecosystem has seen its share of churn in the meantime. Core APIs that frameworks like Vuetify rely on were altered, to the point that even the Migration Build doesn’t cover the differences between Vue 2 and 3. Frameworks such as Nuxt and Quasar have been working to support Vue 3 (with Quasar releasing it’s stable support back in 2021). Meanwhile, work has been going into Vite, which is now the official recommendation for building Vue apps as well (replacing the Vue CLI).
Now that we’ve reached an official recommendation to use Vue 3, what does the future look like for the Vue ecosystem? I asked Twitter what they were looking forward to in the future of Vue, and these are some of the answers that I got.
Reactivity Transform
The Reactivity Transform Unification is the final piece in Vue 3 reactivity primitives and