Vue Vapor mode and Options API

[mezozawahra]

I read an old vue blog that vapor mode will only support composition API, will this be just the initial release and then options API will supported in future releases, and if a project is using vapor mode and some components are written in options api will that cause an error or a fallback where will it cause parts of the application to use VDOM.
It is obvious that vapor mode is the future of vue, so dropping support for Options API seems like killing it and forcing to move to composition api.

[edison1105]

vapor mode will only support composition API

this means the vapor component only supports composition API

in the vapor component, you can render any VDOM component(including components written in options API)
see Playground with vapor branch

[mezozawahra]

Thank you for your reply,
But will options API be supported in the future ? according to vue it is just a layer on top of composition, doesn't that mean options api can be convert to composition api and from there compiled to Vapor code ?

In fact, the Options API is implemented on top of the Composition API! The fundamental concepts and knowledge about Vue are shared across the two styles.

Moreover, many large projects use both composition and options api in it. This will lead to not being able to fully benefit from the Vue Vapor feature which is reducing bundle size by dropping the VDOM reconciliation engine code, and needless not to say DOM manipulation operations performance.

[edison1105]

But will options API be supported in the future ?

Will not support.

If performance is of concern, vapor component should be used entirely instead of the mixed-use of VDOM and vapor components