packages/docs/src/pages/en/blog/april-2025-update.md
This month is packed full of exciting updates and progress across the Vuetify ecosystem.
🖊️ John Leider • 📅 May 1st, 2025
<PromotedEntry />April was a month of execution. Multiple long-standing features landed, foundational work for future flexibility accelerated, and we’re seeing clearer paths emerge around how Vuetify can scale—technically, visually, and in terms of contributor access.
From labs promotions like VNumberInput and VSnackbarQueue, to the start of public-facing infrastructure like @vuetify/mcp, the team is pushing forward on all fronts. This kind of momentum is what sets up big things for the summer and fall—especially as we close in on shipping the new theming engine and continue to clean up performance bottlenecks.
::: success
Cool example of the month: VScrollSelect by J-Sek
:::
The month of April saw the release of "Andromeda", the latest version of Vuetify, which includes a host of new features, improvements, and bug fixes. Most notably, VNumberInput and VSnackbarQueue were promoted from Labs to the Core framework! We've also followed up with several patch releases to address bugs and improve stability.
{ height=150}
Details:
One of the most exciting developments underway is the creation of MCP: Model Context Protocol and our efforts to provide LLMs with the most up to date framework information using it. The @vuetify/mcp package represents our attempt to improve how developers interact with Vuetify through AI and LLM-powered tools.
{ height=500 }
Today, developers often receive outdated or inaccurate help from AI chatbots because these models aren't trained on Vuetify’s latest updates and new innovations we're building. MCP is our answer to that problem.
We want to ensure developers have access to contextually accurate, up-to-date, and deeply integrated Vuetify tools, documentation, snippets and much more right when they need it.
{ height=550 }
This initiative won't just improve AI responses—it will fundamentally change how accessible and powerful Vuetify development can be.
MCP is a major step towards empowering our community even further and we look forward to making the package public soon (like very soon).
Details: @vuetify/mcp
Alongside MCP, another major focus has been Vuetify’s theming system. Our goal is to enable full customization of Vuetify — allowing developers to use any UI library, support long-awaited Material Design 3, and adapt the framework effortlessly to a wide variety of design systems. This includes things such as:
The work happening right now is a foundational step toward that vision. We're targeting an October reveal for this theming overhaul and will be teasing more about it in the months ahead. Here's a small preview of the new theming API in action:
<template>
<v-app>
<v-main>
<v-container>
<!-- Change to a specific theme -->
<v-btn @click="theme.change('dark')">Change to Dark</v-btn>
<!-- Toggle between Light / Dark -->
<v-btn @click="theme.toggle()">Toggle Light / Dark</v-btn>
<!-- Toggle between specific themes -->
<v-btn @click="theme.toggle(['custom', 'light'])">Toggle Custom / Light</v-btn>
<!-- Cycle between all themes -->
<v-btn @click="theme.cycle()">Cycle All Themes</v-btn>
<!-- Cycle between specific themes -->
<v-btn @click="theme.cycle(['custom', 'light', 'utopia'])">Cycle Specific Themes</v-btn>
</v-container>
</v-main>
</v-app>
</template>
<script setup>
import { useTheme } from 'vuetify'
const theme = useTheme()
</script>
These changes focus on expanding Vuetify’s flexibility, making it an even more powerful tool for projects of every scale and style.
Details:
This month, we focused on performance improvements across the board, including saving a bunch of overhead associated with computed caching and call frequency.
For those anticipating the release of VTreeview, there has been movement on an upstream issue that was bottlenecking performance. Once released, we will be able to wrap up the component and move it to the Core framework 🎉.
Details:
From the release of team subscriptions for Vuetify One, to major rewrites of tools like Vuetify Create and the modernized Vuetify Issues site, April was about refining the developer experience across the board. New tooling like @unvuetify is pushing boundaries with Nuxt and auto-import support, and MCP continues to bridge the gap between AI and accurate Vuetify usage.
A major focus has been making Vuetify more accessible to developers at all levels.
Details:
The motivation behind @unvuetify is simple: existing plugins aren’t keeping up with the evolving capabilities of Vue and Nuxt. Features like lazy hydration, auto-importing, and tree shaking are either missing or cumbersome in older tools.
This monorepo isn’t a hard replacement — you can still use vite-plugin-vuetify or webpack-plugin-vuetify if they suit your needs. But if you're working with Nuxt 3, Vue 3.5, or want more flexibility and performance, @unvuetify is built for you.
Created @unvuetify repository to enable:
Details:
We have recently updated Vuetify One to support teams, which allows you to invite up to 25 members to collaborate on your Vuetify projects. This update is designed to share subscription benefits across your team.
{ height=400 }
Subscribe by logging into Vuetify One (top right) and clicking on Subscriptions. If you have any issues or questions, please reach out to us on Discord.
Details: PR#15
Of the many changes coming to Vuetify Play, one of the longest requested features is finally here: router support! This means you can now create and share Vuetify Play projects that include Vue Router, allowing for more complex and interactive examples.
{ height=250 }
We are also in the process of updating the entire Vuetify Play interface to be more intuitive and user-friendly. This includes a new design, improved navigation, and better organization of examples and components. We look forward to sharing more details in the coming months.
Details:
We are wrapping up the new Vuetify Issue Generator, which will replace the current system (still on Vuetify v1.5!).
<video width="100%" height="auto" autoplay loop controls> <source src="https://cdn.vuetifyjs.com/docs/images/blog/april-2025-update/vuetify-issues.mp4" type="video/mp4"></source> </video>The new interface is faster, clearer, and built with Vuetify 3 from the ground up.
May is all about delivery. MCP will ship publicly, and early previews of the new theming system will start rolling out with documentation and migration guides. We're also beginning to lay the foundation for Vuetify 4. The focus is simple: ship real features, reduce friction, and keep moving fast.
More to come next month—stay tuned.