VueConf Toronto 2018 commenced on November 14th. This a three-day event starting from November 14 to 16. One of the speakers at the event was Evan You, the creator of Vue.js who shared what to expect from the yet to be released Vue 3.0.
Day 1 of @VueToronto is a wrap! Stay tuned tomorrow, @jthoms1 will present on using Ionic with @vuejs pic.twitter.com/WvsAGe0zkY
— ionic (@Ionicframework) November 16, 2018
Following are some of the updates that were announced at the conference:
Faster and maintainable code architecture
Vue 3.0 is re-written from the ground up to make its architecture cleaner and more maintainable. To provide better speed some internal functionalities are broken into individual packages in order to isolate the scope of complexity. We can expect 100% faster mounting and patching with this release.
Improved slots mechanism
Now all compiler-generated slots are functions and invoked during the child component’s render call. The dependencies in slots are collected as dependencies of the child instead of the parent. When slot content changes, only the child is re-rendered. And if the parent re-renders, the child does not have to if its slot content did not change. This change prevents useless re-renders by offering even more precise change detection at the component tree level.
Proxy-based observation mechanism
Vue 3.0 will come with a Proxy-based observer implementation that provides reactivity tracking with full language coverage. This will eliminate a number of limitations in the current implementation of Vue 2, which is based on Object.defineProperty:
- Detection of property addition / deletion
- Detection of Array index mutation / .length mutation
- Support for Map, Set, WeakMap and WeakSet
Tree-shaking friendly
The new codebase is tree-shaking friendly. Features such as built-in components and directive runtime helpers can be imported on-demand and tree-shakable. Tree-shakable features also allow the Vue developers to offer more built-in features in future without incurring payload penalties for users that don’t use them.
Easily render-to-native with the Custom Renderer API
Developers will be able to create custom renderers with the Custom Renderer API. They no longer need to fork the Vue codebase with custom modifications. This will allow easily keeping the render-to-native projects like Weex and NativeScript Vue to stay up-to-date with upstream changes. This API will also make it trivially easy to create custom renderers for various other purposes.
In addition to these improvements, it will come with an experimental Hooks API, better warning traces, experimental time slicing support, supports IE11 and improved TypeScript with TSX.
Read more about Vue 3.0 updates from the presentation shared by Evan You.
Read Next
Vue.js 3.0 is ditching JavaScript for TypeScript. What else is new?
Vue CLI 3.0 is here as the standard build toolchain behind Vue applications
