Vue 3 is located in the Pre-Alpha Phase. Yet not all new Features are finished. Some of them have done it now but a step further: Nine RFCs were set on the final comment stage. What does this mean?
Vue.js developed with the Community. That's why the Team provides new Features on GitHub as an RFC, so as Requests for Comments. In the framework of the the RFC process will then be discussed about the Feature and its implementation. Now, where Vue.js 3 has reached the Pre-Alpha Phase changed the Status of some of these RFCs: Nine of them have been set to the Status of „Final Comments“. This is the active Phase with the Merge and implementation in Vue.js if no significant concerns be expressed, after a week. Fundamentally, this Status says that the Core Team considers the RFC proposed Amendment is reasonable and in the Framework to integrate. How Evan You on GitHub stressed, it does not mean that Status, with no Changes to the previously proposed implementation can be made. Details may change in the context of the implementation.
What are the RFCs for Vue.js 3 are almost finished?
Currently, nine of the RFCs are in this last stage of discussion:
- Composition API (revised from #42 Function-based Component API)
- a Custom Directive API Change
- Component v-model API change
- Global mounting/configuration API change
- Render function API change
- Functional and async components API change
- Optional props declaration
- Slots Unification 3.x breaking change
- Replace v-bind’s .sync with a v-model argument
All of which belong to the Vue Core Framework; only two of them are non-Breaking Changes. The Composition API and the optional Declaration of Properties. All other RFCs add new features that are backward-compatible.
An Overview of all RFCs, are in the „Final Comments“ Phase, the appropriate on GitHub. Who would like to say to each listed Pull Requests so something, should do that soon. In a few days, the implementation should begin.