2.1 Architectural Pain Points of Vite 7 and Earlier#

Before Vite 8, Vite used a dual-bundling mechanism:

While this architecture was the best choice at the time, it had a fundamental problem: “a crack in the armor.”

The two workflows always had inconsistencies:

• Code that runs in development may error after building
• Plugins may behave differently during development and build phases
• Developers need to maintain two sets of configuration logic simultaneously

2.2 The Rise of the Rust Toolchain#

Meanwhile, Rust rose rapidly in the frontend toolchain space:

• esbuild (Go) had already proven the performance advantages of compiled languages in build tools
• Turbopack (Rust) demonstrated the possibilities of incremental compilation
• Rspack (Rust) proved thatextreme performance could be achieved while maintaining Webpack ecosystem compatibility

Rust, with a 32% project share, has become the preferred language for systems tool development.

3.1 What Is Rolldown?#

Rolldown is a project initiated by Vite creator Evan You, with the goal of rewriting Rollup in Rust, achieving:

1. Rollup plugin API compatibility: Seamless migration of the existing ecosystem
2. Performance rivaling esbuild: Extreme build speed
3. Unified development and build workflow: Eliminating inconsistencies

3.2 Rolldown’s Technical Advantages#

1
Rolldown Architecture
2
├── Rust Core Engine
3
│   ├── Fast Parsing
4
│   ├── Efficient Transformation
5
│   └── Optimized Bundling
6
├── Rollup Plugin Compatibility Layer
7
│   ├── Plugin API Mapping
8
│   └── Hook System Adaptation
9
└── Vite Integration
10
    ├── Development Server
11
    └── Production Build

Performance comparison:

4.1 Development Experience Improvements#

1
#See browser console.log directly in the terminal
2
$ pnpm dev
3

4
[vite] Browser console:
5
  → Component rendered in 12ms
6
  → API response: 200 OK

4.2 Built-in TypeScript Support#

Vite 8 natively supports TypeScript with no additional configuration needed:

1
// tsconfig.json
2
{
3
  "compilerOptions": {
4
    "paths": {
5
      "@/*": ["./src/*"]  // ✅ Native support in Vite 8
6
    },
7
    "emitDecoratorMetadata": true  // ✅ No external plugin needed
8
  }
9
}

4.3 @vitejs/plugin-react v6#

The React plugin receives a major update:

• Oxc integration: No longer depends on Babel
• Faster compilation speed: Rust-driven transformation
• Smaller dependency footprint: Reduced node_modules size

1
import { defineConfig } from 'vite';
2
import react from '@vitejs/plugin-react';
3

4
export default defineConfig({
5
  plugins: [react()],  // Automatically uses Oxc transform
6
});

4.4 Enhanced WASM Support#

.wasm?init imports can now run in SSR environments:

1
// Works on both client and SSR
2
import init from './module.wasm?init';
3

4
const instance = await init();

4.5 Vite Plugin Official Website#

A new Vite Plugin official website has been added, making it easy to search for plugins in the Vite ecosystem.

5.1 Upgrade Steps#

1
# 1. Upgrade Vite
2
npm install vite@latest
3

4
# 2. Upgrade the React plugin
5
npm install @vitejs/plugin-react@latest
6

7
# 3. Check plugin compatibility
8
npx vite --config vite.config.ts

5.2 Breaking Changes#

5.3 Configuration Example#

1
import { defineConfig } from 'vite';
2
import react from '@vitejs/plugin-react';
3
import vue from '@vitejs/plugin-vue';
4

5
export default defineConfig({
6
  plugins: [
7
    react(),  // or vue()
8
  ],
9

10
  // New Vite 8 config
11
  future: {
12
    v6devTransformer: true,  // Enable the new transformer
13
  },
14

15
  // Rolldown build config
16
  build: {
17
    rollupOptions: {
18
      output: {
19
        format: 'es',
20
        sourcemap: true,
21
      },
22
    },
23
  },
24
});

6.1 Impact on Developers#

• Faster development experience: HMR down to ~10ms, nearly instant feedback
• More consistent builds: Development and build use the same engine
• Simpler configuration: No need to maintain two sets of configs

6.2 Impact on Frameworks#

6.3 Impact on the Plugin Ecosystem#

• Most existing Rollup plugins are compatible
• New plugins can directly use the Rolldown API
• Plugin performance generally improved by 5-10x

7.1 Test Project#

• Project type: Medium-to-large React application
• Component count: ~500
• Lines of code: ~100,000
• Dependency count: ~80

7.2 Test Results#

8.1 The VoidZero Plan#

The VoidZero plan led by Evan You is advancing:

• Rolldown: Unified build tool
• Oxc: Fast JavaScript toolchain
• Nuxt acquisition: Expanding the Vue ecosystem

8.2 The Rust Toolchain Trend#

The Rustification of frontend toolchains in 2026 is a foregone conclusion: