Vuetify 3 useVuetify() performance in large-scale applications

Vuetify 3 Global Plugin Access Pattern

Vuetify 3 introduced the useVuetify() composable to replace Vuetify 2's mixin-based global access patterns. This composable provides reactive access to the Vuetify instance and its utilities like $, for theme, typography, and icons. The migration guide indicates this is the recommended approach for accessing Vuetify's global features within setup() functions.

The unresolved decision concerns whether the new useVuetify() composable fully replaces all Vuetify 2's mixin-based global access patterns without performance regression in large applications. Vuetify 2's mixins were resolved once during component initialization, while Composition API composables may introduce different reactivity overhead patterns that scale differently with application size.

Key questions:

• Does useVuetify() introduce measurable performance overhead compared to Vuetify 2 mixins in applications with 100+ components using global Vuetify features?
• How does the reactivity tracking in useVuetify() scale with deeply nested component trees that frequently access theme or icon properties?
• Are there documented benchmarks or performance profiles comparing Vuetify 2 mixin resolution versus Vuetify 3 composable resolution patterns?