Will Vuetify ever be able to support Vapor Mode in Vue 3.6+ ?

[craigrileyuk]

I noticed that when using Vapor Mode in the pre-release version of Vue that you cannot use getCurrentInstance, which Vuetify relies heavily upon.

Will it ever be possible for Vuetify to support this mode? At the moment I can't even use just a VApp wrapper in my project since it immediately hits this error:

Uncaught Error: [Vuetify] provideTheme must be called from inside a setup function
    getCurrentInstance getCurrentInstance.js:7
    provideTheme theme.js:363
    setup VApp.js:23
    setup defineComponent.js:28

[abumalekFayed]

I think this will be done when vue 3.6 released.

[J-Sek]

Typical apps that ship with Vuetify (at least from my experience) are admin panels, CRUD, dashboards, forms, B2B sites, etc. In these usage scenarios rendering and initial load is usually irrelevant in comparison to networking and data access overhead. Assuming your team already optimized and eliminated backend bottlenecks, there are plenty of things that you can do to improve perceived performance:

• VVirtualScroller
• v-intersect / v-lazy
• preload/cache images
• load less data (require explicit "load more" clicks or reorganize UI to optimize for actual usage patterns)

What Vapor promises is smaller bundle and speed gains for heavy real-time data visualization. Once it ships officially, we hope charting libraries and spreadsheet-like components are going to pick it up first. I have some doubts if it can actually impact Vuetify users. The "why is my UI slow" scenarios reported from real-life were mostly "loading 100x form inputs" which is usually a mistake - slapping Vapor won't fix it.

If you already have established project where Vuetify lags and hurt user experience, do not hesitate to reach the team on Discord.

Alternatively you can spend time to pick up #22483, experiment and help us deliver the Vapor support sooner that later ;) Some features depend on community engagement.