Evan You Announces: Vue 3.6 Released, Vue 4.0 Launched, Vite 8 Already Landed

On July 18, 2026, at Vue&ViteConf 2026 in Shanghai, Evan You announced three things in one go: Vue 3.6 is officially released, Vue 4.0 has been initiated, and Vite 8 has fully landed. On this day, the Vue ecosystem unveiled three eras simultaneously — the performance era, the AI era, and the layered rendering era.

1. Vue 3.6: Officially Released, Performance Core Swap

On July 18, 2026, at Vue&ViteConf 2026 in Shanghai. Evan You took the stage and announced the first piece of news: Vue 3.6 is officially released.

This day came over five months after the first beta version was released on February 6, 2026. The Vue team spent more than five months polishing the beta, releasing a total of 17 beta versions, ultimately delivering an answer that electrified the entire audience.

1.1 Vapor Mode: Virtual DOM Becomes Optional

Vapor Mode is the most core change in Vue 3.6. It allows developers to add a vapor attribute to <script setup>, and the component will skip the virtual DOM and directly manipulate the real DOM.

<script setup vapor>
import { ref } from 'vue'
const count = ref(0)
</script>

<template>
  <button @click="count++">Clicked {{ count }} times</button>
</template>

With Vapor Mode enabled, rendering speed increases by up to 97%, bundle size shrinks by 20-50%, and initial load JS volume decreases by about two-thirds. 100,000 components can be mounted within 100ms — Vue stands in the same performance tier as SolidJS.

Vapor Mode adopts a per-component design, allowing component-by-component selection — Vapor components and virtual DOM components can freely coexist in the same component tree, achieving seamless interoperability via the vaporInteropPlugin.

1.2 alien-signals: Reactivity Engine Replacement

alien-signals is the other major core change in Vue 3.6. This library, only 1KB after compression, was directly ported back into Vue 3.6's core codebase.

alien-signals employs a Push-Pull hybrid algorithm: when a reactive state changes, the signal "pushes" change information down the dependency graph, marking computed properties that depend on this state as "dirty"; only when a computed property or view actually needs to read the updated value does it "pull" upward on demand and recalculate the result.

In most cases, a state change does not cause all dependent computed properties to be read. The Push-Pull algorithm avoids the inefficient path of "recalculate everything first, then determine if needed," executing recalculation only when truly necessary.

According to benchmark data: Vue 3.6 is about 4 times faster than 3.4, about 1.8 times faster than 3.5, computed throughput is over 30 times higher, and memory usage is reduced by 65%. In real benchmark tests, for a complex list containing 10,000 components, the frame rate stability of an alien-signals-driven application far exceeds Vue 3.5.

Vue 3.6 has simultaneously swapped out both the rendering engine and the reactivity engine.

1.3 Comparison with React 19

In 2026, both React 19 and Vue 3.6 completed major architectural upgrades. React 19 took the route of "server components + automatic compilation optimization" — through RSC, Actions API, and React Compiler, handing state management, form logic, and rendering optimization that previously required manual handling over to the framework for automatic completion.

Vue 3.6 took the route of "reactive bottom-layer reconstruction + compile-time rendering optimization" — reconstructing the reactivity engine through alien-signals, and skipping the virtual DOM through Vapor Mode.

The two paths are completely different, but the goal is the same: reduce the mental burden on developers and raise the upper limit of application performance.

1.4 Upgrade Cost: Nearly Zero

Vue 3.6 has no breaking changes. Upgrading from Vue 3.5 to 3.6 requires no modification of any existing code:

npm install vue@latest

One npm install, get a 4x performance boost for free.

2. Evan You Announces: Vue 4.0 Launched

More shocking than the Vue 3.6 release was the second piece of news Evan You announced: Vue 4.0 is officially initiated.

2.1 Why Vue 4.0?

Evan You explicitly stated that the core goals of Vue 4.0 are to stabilize Vapor Mode and expand its support scope, explore compile-time reactivity and experimental WebAssembly support, and provide more complete cross-version migration tools.

2.2 Migration Cost Will Be Extremely Low

Evan You has repeatedly emphasized on many occasions: "The migration cost for Vue 4 will be kept extremely low." The reason this is possible is that Vue 3 laid the groundwork for progressive upgrades from the very beginning of its design.

2.3 Timeline Speculation

Based on signals released so far, Vue 4.0 is expected to enter the Beta phase in the second half of 2026 (currently planned around Q3), with a potential RC release before the end of the year.

3. Vite 8: Fully Landed

3.1 From Dual Engine to Single Engine

The most core change in Vite 8 is: using Rolldown to uniformly replace the previously used esbuild for development environments and Rollup for production environments.

Rolldown is a high-performance JavaScript bundling tool based on Rust, 10-30 times faster than Rollup. Vite 8 maintains full plugin compatibility.

3.2 Real Project Data

• Linear: 46 seconds → 6 seconds (↓87%)
• Ramp: Build time reduced by 57%
• Beehiiv: Build time reduced by 64%
• A developer: 4 minutes → 30 seconds (8x)
• A million-line project: 12 minutes → 2 minutes (6x)

3.3 Vite+: The Next Step

In his speech, Evan You also mentioned Vite+ — an end-to-end frontend toolchain implemented in Rust. Vite+ will natively rewrite the compiler, bundler, server, and deployment toolchain entirely in Rust, with the goal of keeping frontend development responsive at the millisecond level from project creation to deployment online.

4. Viewing the Three Things Together

Trend 1: The Frontend is Entering the "Compile-Time + Runtime" Dual Engine Era

Vapor Mode is compile-time optimization, alien-signals is runtime optimization, and Vite 8+Rolldown is build-time optimization. Vue is pushing the "slow" parts down to the infrastructure layer, leaving "fast" for the developer experience layer.

Trend 2: The Frontend is Moving from "For Humans" to "For AI"

Vue 3.6's Vapor Mode makes AI-generated code run faster and lighter. Vite 8 increases the speed of AI-built projects by 10-30 times. The stabilization of Vapor Mode in Vue 4.0 will provide AI Agents with a more efficient component rendering engine.

Vue 3.6's Vapor Mode and alien-signals are turning Vue into a "performance machine" extremely friendly to AI Agents.

Trend 3: Frontend Frameworks are Undergoing "Bottom-Layer Core Swaps"

From TypeScript 7.0 rewritten in Go, to Astro 7 rewriting its compiler in Rust, to Vite 8 using Rust's Rolldown to replace Go's esbuild+rollup — the frontend toolchain is comprehensively shifting from "writing tools in JavaScript" to "writing tools in Rust." Vue 3.6's alien-signals is a manifestation of this trend at the reactivity level.

Final Words

On July 18, 2026, at Vue&ViteConf 2026 in Shanghai, Evan You announced three things in one day:

Vue 3.6 is officially released — Vapor Mode makes the virtual DOM optional, alien-signals makes the reactivity system 4 times faster.

Vue 4.0 is initiated — the next major version has already begun.

Vite 8 has fully landed — Rolldown increases build speed by 10-30 times.

These three things together convey a clear signal: Vue is evolving from a "progressive framework" into a "performance machine + AI-friendly platform."

Vue 3.6 is not an ordinary version update. It is the watershed moment where the Vue ecosystem moves from "for human developers" to "for AI and humans together."

Vue 3.6 is already usable. Vue 4.0 is on its way. And you, are you ready?

Let's chat in the comments: When do you plan to upgrade to Vue 3.6? Which project do you most want to use Vapor Mode in?