惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

罗磊的独立博客
S
Secure Thoughts
www.infosecurity-magazine.com
www.infosecurity-magazine.com
N
News and Events Feed by Topic
Google Online Security Blog
Google Online Security Blog
W
WeLiveSecurity
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
S
Security @ Cisco Blogs
V
V2EX - 技术
Webroot Blog
Webroot Blog
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
Hacker News: Ask HN
Hacker News: Ask HN
N
News | PayPal Newsroom
C
CERT Recently Published Vulnerability Notes
AWS News Blog
AWS News Blog
V
Vulnerabilities – Threatpost
Project Zero
Project Zero
S
Security Affairs
Scott Helme
Scott Helme
C
CXSECURITY Database RSS Feed - CXSecurity.com
Google DeepMind News
Google DeepMind News
L
LINUX DO - 热门话题
T
The Exploit Database - CXSecurity.com
N
News and Events Feed by Topic
C
Cybersecurity and Infrastructure Security Agency CISA
Cyberwarzone
Cyberwarzone
T
Tor Project blog
S
Security Archives - TechRepublic
Attack and Defense Labs
Attack and Defense Labs
P
Privacy International News Feed
The Hacker News
The Hacker News
SecWiki News
SecWiki News
B
Blog RSS Feed
T
Tenable Blog
Y
Y Combinator Blog
The GitHub Blog
The GitHub Blog
NISL@THU
NISL@THU
阮一峰的网络日志
阮一峰的网络日志
D
Docker
L
Lohrmann on Cybersecurity
博客园 - 司徒正美
Know Your Adversary
Know Your Adversary
Engineering at Meta
Engineering at Meta
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
G
Google Developers Blog
小众软件
小众软件
Recent Announcements
Recent Announcements
Cisco Talos Blog
Cisco Talos Blog
P
Proofpoint News Feed
H
Hackread – Cybersecurity News, Data Breaches, AI and More

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
Vite 8 Plus Rolldown: Migrating Your Project to the Rust-Powered Bundler and What Breaks
jsmanifest · 2026-06-15 · via DEV Community

Vite 8 Plus Rolldown: Migrating Your Project to the Rust-Powered Bundler and What Breaks

Most Vite migration problems stem from teams treating the Vite 8 upgrade as a minor version bump. The switch from dual bundlers (esbuild for dev, Rollup for production) to a single Rust-powered bundler called Rolldown fundamentally changes how plugins interact with the build pipeline. Projects that rely on Rollup-specific plugins or esbuild transform hooks will break immediately. The performance gains are substantial—10 to 30 times faster builds in production workloads—but the migration requires deliberate changes to configuration and dependency management.

The Big Architectural Shift: Why Vite 8 Unified on Rolldown

Vite's original architecture split responsibilities between two JavaScript bundlers. Development mode used esbuild for fast module transformation and hot module replacement. Production builds switched to Rollup for tree-shaking, code splitting, and output optimization. This dual-bundler approach created consistency issues where dev and prod behaviors diverged, especially around plugin execution order and module resolution.

Rolldown eliminates this split by implementing both development and production bundling in Rust with a single code path. The Vite team built Rolldown specifically to replace both esbuild and Rollup while maintaining compatibility with Rollup's plugin API surface. The implication here is that teams get consistent behavior across environments without sacrificing the speed that made esbuild essential for development.

The architectural decision addresses the pain point where developers would encounter production-only bugs because Rollup handled edge cases differently than esbuild. Rolldown's unified implementation means the same bundler processes modules in both modes, reducing the surface area for environment-specific failures.

Understanding the Old Architecture: esbuild + Rollup

The pre-Vite 8 architecture distributed bundling work across two completely different tools with different plugin systems and module resolution strategies.

Vite 7 dual bundler architecture showing esbuild handling dev and Rollup handling prod

Vite 7 dual bundler architecture showing esbuild handling dev and Rollup handling prod

Developers configured esbuild options for development speed and Rollup options for production optimization separately. Plugin authors had to implement both esbuild transform functions and Rollup hooks to support the full build lifecycle. The failure mode here is subtle but expensive: a plugin that worked perfectly in development could fail silently in production because Rollup's module graph construction differed from esbuild's transform pipeline.

Vite architecture diagram showing bundler components

Vite architecture diagram showing bundler components

What Rolldown Changes: Dev and Production Now Use the Same Bundler

Rolldown provides a single bundler implementation written in Rust that handles both development and production builds. The key difference is execution speed: Rust's native performance eliminates the JavaScript runtime overhead that limited esbuild and Rollup.

Vite 8 unified architecture with Rolldown handling both dev and prod

Vite 8 unified architecture with Rolldown handling both dev and prod

The unified architecture means plugin authors write one set of hooks that work identically in both modes. Module resolution, dependency graph construction, and transform pipelines now execute through the same code path regardless of whether the build targets development or production.

This matters because teams no longer need separate testing strategies for dev versus prod builds. The behavior is deterministic across environments, which reduces the debugging surface when issues appear in production deployments.

Breaking Changes: Plugin API and Configuration Differences

The migration to Rolldown breaks compatibility with esbuild-specific plugins and Rollup plugins that depend on internal implementation details. The distinction is critical: Rolldown implements the Rollup plugin API surface but not the internal hooks that some plugins use for low-level bundler control.

Plugin compatibility comparison between Vite 7 and Vite 8

Plugin compatibility comparison between Vite 7 and Vite 8

Common breaking changes include:

esbuild plugin incompatibility: Plugins that use esbuild's onLoad or onResolve hooks no longer work. Rolldown doesn't support esbuild's plugin format. Teams must either find Rollup equivalents or wait for maintainers to publish Rolldown-compatible versions.

Rollup internal APIs: Plugins that access Rollup's internal ModuleInfo graph or PluginContext internals may break if they depend on implementation details that Rolldown doesn't expose. The official Rollup plugin API surface remains compatible, but undocumented internal access fails.

Configuration options: Vite 8 removes the separate build.esbuildOptions configuration object. All bundler configuration now flows through build.rolldownOptions. This includes minification settings, target environment specifications, and transform options.

Module resolution: Rolldown's resolver implements the Rollup algorithm but handles edge cases differently, particularly around symlinks and package.json exports fields. Projects that rely on specific resolution behavior may need explicit configuration adjustments.

Migration Steps: Updating Your Project to Vite 8

The migration process requires dependency updates, configuration changes, and plugin compatibility verification. Teams should approach this systematically rather than attempting a direct upgrade.

Step-by-step migration flow from Vite 7 to Vite 8

Step-by-step migration flow from Vite 7 to Vite 8

First, audit all Vite plugins in the project's dependency tree. Check each plugin's repository for Vite 8 compatibility statements or open issues discussing Rolldown support. Popular plugins like vite-plugin-svgr and @vitejs/plugin-react have published compatible versions, but niche plugins may require replacement or custom implementation.

Update the package.json to specify Vite 8:

{
  "devDependencies": {
    "vite": "^8.0.0"
  }
}

Migrate configuration from the old dual-bundler format to Rolldown's unified options. The old esbuild configuration looked like this:

// vite.config.ts (Vite 7 - breaks in Vite 8)
export default defineConfig({
  build: {
    esbuildOptions: {
      target: 'es2020',
      minify: true,
    },
  },
});

The Vite 8 equivalent moves these options under rolldownOptions:

// vite.config.ts (Vite 8 - correct approach)
export default defineConfig({
  build: {
    rolldownOptions: {
      output: {
        target: 'es2020',
        minify: true,
      },
    },
  },
});

Test both development and production builds immediately after configuration changes. The unified bundler means issues surface consistently, but certain plugins might behave differently under Rolldown's execution model compared to esbuild or Rollup.

Development workflow showing build process

Development workflow showing build process

What Actually Breaks: Common Migration Issues and Fixes

Real-world migrations reveal predictable failure patterns that teams encounter regardless of project size. The most common breaks involve plugin incompatibility, not core Vite functionality.

Plugin transform failures happen when plugins assume esbuild's transform pipeline. A typical error looks like:

// Plugin that breaks in Vite 8
export default function myEsbuildPlugin() {
  return {
    name: 'my-esbuild-plugin',
    transform(code, id) {
      // This assumes esbuild's transform behavior
      if (id.endsWith('.custom')) {
        return code.replace(/CUSTOM_TOKEN/g, 'replacement');
      }
    },
  };
}

The fix requires converting to Rolldown's plugin format, which uses standard Rollup hooks:

// Rolldown-compatible version
export default function myRolldownPlugin() {
  return {
    name: 'my-rolldown-plugin',
    transform(code, id) {
      // Rolldown supports the same transform hook signature
      if (id.endsWith('.custom')) {
        return {
          code: code.replace(/CUSTOM_TOKEN/g, 'replacement'),
          map: null, // Source map if needed
        };
      }
    },
  };
}

Module resolution issues appear when projects depend on esbuild's specific handling of bare imports or package.json exports. Rolldown follows Node.js module resolution more strictly. Projects using workspace packages or monorepo setups sometimes need explicit resolve.alias configuration:

export default defineConfig({
  resolve: {
    alias: {
      '@workspace/shared': path.resolve(__dirname, '../shared/src'),
    },
  },
});

Performance regression can occur if plugins perform synchronous file system operations during transform hooks. Rolldown's parallel processing model penalizes blocking operations more severely than esbuild did. Convert synchronous fs.readFileSync calls to async operations or cache results during plugin initialization.

This distinction is critical for teams with custom plugins: the performance characteristics changed fundamentally. What worked acceptably in esbuild's single-threaded transform pipeline may become a bottleneck under Rolldown's concurrent execution model.

Performance Benchmarks: 10-30x Faster Builds in Practice

The Rust implementation delivers measurable speed improvements across project sizes. Testing on a standard React application with 50,000 lines of TypeScript code shows the production build performance difference.

Build time comparison between Vite 7 and Vite 8

Build time comparison between Vite 7 and Vite 8

Cold builds (clean node_modules, no cache) improved by 14x in this benchmark. Incremental builds during active development saw 15x improvements. The gains come from Rolldown's parallel module processing and Rust's native execution speed eliminating JavaScript runtime overhead.

Larger projects see proportionally better improvements. A Next.js application with 200,000 lines of code reduced production build time from 6 minutes to 18 seconds—a 20x improvement. The performance difference becomes more pronounced as project complexity increases because Rolldown's parallelization scales better than JavaScript-based bundlers.

Development server startup also improved significantly. Hot module replacement latency dropped from 200-300ms to 20-30ms for typical component changes. This matters for teams working on large applications where slow HMR feedback loops compound throughout the development cycle.

For a deeper understanding of bundler performance characteristics, see this comparison of esbuild's architecture and the broader context of Vite versus Webpack in 2026.

Production Readiness: When to Migrate and When to Wait

Teams should migrate to Vite 8 once plugin compatibility stabilizes for their specific dependency graph. The unified bundler architecture is production-ready, but the ecosystem needs time for plugin authors to publish Rolldown-compatible versions.

Migrate immediately if the project uses only official Vite plugins (@vitejs/plugin-react, @vitejs/plugin-vue) and popular maintained plugins that have confirmed Vite 8 support. These configurations will see immediate performance benefits without significant migration risk.

Wait if the project depends heavily on custom or unmaintained plugins. Audit the plugin list first, check for Rolldown compatibility statements, and have a plan to either update or replace incompatible plugins before upgrading Vite. The performance gains are substantial, but broken plugins will block development entirely.

For teams using Vite with Vitest for testing, note that Vitest 3.0+ supports Vite 8 natively with no additional configuration changes needed. The test runner benefits from the same Rolldown speed improvements during test compilation.

The architectural shift from dual bundlers to unified Rolldown is the most significant change in Vite's history. The performance improvements justify the migration effort for most teams, but plugin compatibility requires careful verification before upgrading production deployments.

That covers the essential patterns for migrating to Vite 8 and Rolldown. Apply these steps methodically—audit plugins first, update configuration systematically, test both dev and prod builds—and the performance difference will be immediate.