Vue 3 is now in RC! #189
Vue 3 is now in RC!
We are very excited to announce that Vue 3.0 has entered RC (Release Candidate) stage!
Entering the RC stage means that both the API and implementation of Vue 3 core have stabilized. In principle, we do not expect to introduce new major features or breaking changes before the final release. Most official framework parts also now have v3 support. Please check here for the latest status.
The Vue docs team have been updating our docs for v3 and it is now available at v3.vuejs.org! It has been a massive undertaking and many thanks to the hard work by the docs team: @NataliaTepluhina, @bencodezen, @phanan and @sdras. The new docs has been meticulously migrated to cover differences between v2 and v3, runs on VuePress, and has improved code samples that can be edited inline.
For a quick overview on what's new and what's changed, please refer to the Migration Guide.
Please note that the new documentation, especially the Migration Guide, is still a work in progress, and we will continue to polish it throughout the RC stage.
Initial DevTools Support for v3
We have also published a beta version of the new Vue Devtools with initial v3 support, thanks to the amazing work by @Akryum.
The devtool has received a major refactor to better decouple its core logic from different supported Vue versions. The interface also has a new look implemented with Tailwind CSS. Currently, only component inspection is supported - but more features will be coming soon.
Update: Devtools beta has been approved and now available on the Chrome Web Store (Note: the devtools requires
Trying It Out
If you are interested in trying out Vue 3 today, there are a few ways to do it:
We haven't been able to complete full IE11 support for the RC, so we will continue to work on that.
At the same time, our primary focus will shift to documentation, migration, and compatibility. Our current goal is to provide clear documentation for starting new projects with v3, and help library authors upgrade their packages to support v3. The docs team will continue to polish the migration guide and v3 documentation based on feedback from the community.
Migrating non-trivial applications from v2 to v3 will likely be a much slower process. We will provide code mods and tools to help with such migrations, but in most cases, this will depend on how fast the project's dependencies can be upgraded to support Vue 3. It is also important to evaluate whether the risk and time investment of upgrading is worth it - since Vue 2 will continue to be supported. We plan to dedicate a focus period after 3.0 release to back-port features into v2 via compatibility plugins. We are already seeing success with this approach in @vue/composition-api.
There are a few features that are shipped in the RC release, but have been marked experimental:
These features are shipped now in order to collect feedback from actual usage, but they may still receive breaking changes / major adjustments. They will likely remain experimental in 3.0, and become finalized as part of 3.1.
The text was updated successfully, but these errors were encountered: