The new composition API is pretty sweet, but there’s plenty of reasons not to write an article around it for this purpose.

For starters, it’s not been released yet, and I don’t really want to ask users to install an unrelated dependency.

Most users are not yet familiar with the composition API, and it’s designed for more advanced use-cases. Why introduce unnecessary complexity and learning curve when that is not the point of the article?

Most of the logic is vanilla JavaScript happening in the mounted hook. The only thing the composition API would really affect is the computed props and how the mounted hook is initialized. But I don’t think there would actually be much gain to using it.

I am really looking forward to V3 though :)

Full Stack @Revealbio | Author of Vuetensils & Particles CSS | Panelist @ViewsOnVue | Board Member @sandiegojs

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store