I'll be honest with you: I'm biased. I've been building with Vue since the early days, back when Vue 1.x was still a one-person side project and the rest of the world hadn't noticed yet. I watched it grow from a lightweight alternative to Angular into one of the most beloved frameworks in the JavaScript ecosystem, and then mature into the powerhouse that Vue 3.x is today. This post is partly a love letter and partly a practical guide. I want to show you what Vue 3 looks like at its best in 2026: the latest version, the patterns that make it shine, and real code examples you can steal immediately. ## A quick history, because context matters Vue was created by Evan You, who released the first public version in February 2014. It grew organically through community love rather than corporate backing, no Google or Facebook money behind it, just a framework that developers genuinely enjoyed using. I came to Vue relatively early, when it was still being dismissed by a lot of people as "just a nice template system." What drew me in was how approachable it felt. You could drop a script tag into an HTML file and have a working reactive component in five minutes. But it also scaled, the more you invested in learning it, the more expressive and powerful it became. Vue 3 launched in September 2020. It was a ground-up rewrite: new reactivity system, TypeScript-first internals, the Composition API, ` ``` ```vue ``` The ` ``` With `defineModel()`: ```vue ``` That's it. `defineModel()` returns a ref that automatically syncs with the parent's `v-model`. You can use it directly with `v-model` on native inputs. ## useTemplateRef: typed template refs (Vue 3.5) Template refs used to have a slightly awkward API. In Vue 3.5, `useTemplateRef()` was introduced to make them explicit and properly typed. ```vue ``` The TypeScript generic gives you proper autocomplete on `inputEl.value`. Small improvement, big developer experience win. ## Reactive props destructure (Vue 3.5) This one removes a persistent gotcha that tripped up newcomers for years. In Vue 3.5, you can destructure props reactively: ```vue ``` You can even set default values inline, replacing the `withDefaults` wrapper entirely. ## Teleport: rendering outside your component tree One of my favourite Vue 3 features that doesn't get enough credit is Teleport. It lets you render a piece of template somewhere else in the DOM, typically the body, while keeping the component logic where it belongs. Classic use case: a modal that needs to render at the top of `` to avoid CSS stacking context issues, but whose open/close state lives inside a component deep in your tree. ```vue ``` No portals library needed. No manual DOM manipulation. Vue handles it cleanly. ## Pinia: the official state management solution If you're using Vuex, please migrate to Pinia. Pinia has been the officially recommended state management library for Vue since 2022, and it is better in every way: simpler API, TypeScript out of the box, proper devtools integration, no mutations, no nested modules. ```typescript // stores/useUserStore.ts import { defineStore } from 'pinia' import { ref, computed } from 'vue' export const useUserStore = defineStore('user', () => { const user = ref(null) const isLoggedIn = computed(() => user.value !== null) async function login(email: string, password: string) { user.value = await api.login(email, password) } function logout() { user.value = null } return { user, isLoggedIn, login, logout } }) ``` Notice it uses the Composition API syntax: `ref`, `computed`, functions. Your stores look and feel like composables. No `mapState`, no `mapGetters`, no `commit`. Just a reactive object. ## The ecosystem Vue doesn't exist in a vacuum. These are the tools I use with it on every serious project. **Vite** is the official build tool recommended by Vue. Instant dev server starts, lightning-fast HMR, ES module-native. I will never go back to webpack. **Vue Router** supports the Composition API via `useRouter()` and `useRoute()`, with full TypeScript support. **VueUse** is a massive collection of ready-made composables. `useStorage`, `useDark`, `useIntersectionObserver`, `useDebounce`, and over 200 more. If you're writing a composable from scratch, check VueUse first. **Nuxt 3** adds file-based routing, auto-imports, server routes, and more on top of Vue 3. If you need SSR, SSG, or a full-stack framework, Nuxt 3 is mature, fast, and excellent. ## Vue 3.5 at a glance: the feature highlight reel Here's a quick reference of the biggest improvements across recent Vue 3.x releases. Vue 3.3 brought generic components with `defineProps()` complex types, `defineEmits` complex type support, and `defineSlots` for typed slot definitions. Vue 3.4 shipped the `defineModel()` macro, a 2x faster template compiler rewrite, improved reactivity tracking, and the `v-bind` same-name shorthand (`:id` instead of `:id="id"`). Vue 3.5 introduced reactive props destructuring, `useTemplateRef()` for typed template refs, `useId()` for generating unique accessible IDs, lazy hydration strategies for components, and memory usage improvements in large reactive trees. The lazy hydration strategies in 3.5 are particularly interesting for SSR/Nuxt users. You can now defer hydrating heavy components until they're visible in the viewport, giving you significantly faster Time to Interactive on content-heavy pages. ## Wrapping up Vue 3.5 is the best Vue has ever been, and I say that having been here for most of the journey. The Composition API is mature, the tooling is excellent, the ecosystem is healthy, and the framework is fast in a way that rarely requires you to think about it. If you're already a Vue developer, I hope the code examples in this post gave you something to take back to your projects, especially `defineModel`, reactive props destructure, and `useTemplateRef` if you haven't tried them yet. If you're considering Vue for a new project: yes. Build the thing. The learning curve is gentle, the ceiling is high, and the developer experience is, in my completely unbiased opinion, among the best in the JavaScript ecosystem.

Hello from a teleported modal!

Developer Blog

Posts tagged "composition-api"

Vue 3 in 2026: Why I'm Still All-In After All These Years