Rolldown 1.0 Release Candidate Lands — a Rust-powered bundler for Vite and the web

VoidZero published the Rolldown 1.0 Release Candidate on January 21, 2026 — a production‑focused, Rust‑based JavaScript/TypeScript bundler that the Vite team is adopting to replace the previous esbuild + Rollup split. Rolldown declares API stability in this RC and advertises broad Rollup plugin compatibility plus large performance gains (the project cites 10–30× faster production bundling vs. Rollup in common workloads). (voidzero.dev)

Why this matters for full‑stack teams

• Unified dev→prod pipeline: Vite historically used esbuild for dev and Rollup for production, creating subtle semantic differences between development and production builds. Rolldown aims to eliminate that divergence by serving both roles from a single, high‑performance engine.
• Immediate build-time wins: Teams with large bundles or monorepos should expect shorter CI build times and faster production build iterations; early results show material reductions in wall time and memory use.
• Plugin and workflow compatibility: Rolldown targets Rollup's plugin API, so many existing plugins should work with minimal changes — but non‑trivial plugins (those that rely on esbuild internals, custom AST transforms, or native Rollup internals) will need verification.
• New capabilities: The RC documents features aimed at large apps and libraries — module‑level persistent caching, more granular chunking controls (output.codeSplitting), and planned native bridges for AST and MagicString-style transforms — which enable more predictable chunking and faster incremental builds.

Practical checklist for teams (what to do this week)

1. Smoke test with a forked branch: run full production builds and CI on a feature branch using the Rolldown 1.0 RC (or Vite 8 beta which defaults to Rolldown). Compare build time, bundle sizes, and CI memory/CPU usage.
2. Test critical plugins: verify any Rollup/Vite plugins you rely on (CSS extraction, image transforms, d.ts generators, custom plugin hooks). Pay special attention to plugins that call internals or depend on esbuild-specific behavior.
3. Validate runtime output: run end-to-end tests and production staging deployments — check chunk loading, code‑splitting boundaries, lazy imports and SSR hydration paths for behavior parity.
4. Audit CI caching: update caching keys to include Rolldown/Vite version; persistent module‑level caches may let you simplify or reduce cache scope, but verify cache invalidation semantics.
5. Prepare a rollback plan: keep a pinned dependency path to the current Vite/esbuild+Rollup setup in case you need to revert quickly after discovering regressions.

Migration notes & gotchas

• Expect small config adjustments: some esbuild/Rollup flags map differently; consult the Vite migration guide and rolldown compatibility notes before mass upgrades.
• Large monorepos: Rolldown’s persistent cache and bundle strategies can yield disproportionate gains, but initial configuration (entry graph and chunking rules) may need tuning for predictable chunk layouts.
• Third‑party frameworks/tools: If you use frameworks or CI tools that embed Vite (e.g., Astro, Nuxt, framework integrations), coordinate overrides or pin versions in package manifests during evaluation — these embedded consumers may not immediately opt into Rolldown.

Bottom line Rolldown 1.0 RC is a meaningful milestone for JavaScript tooling: it promises to simplify the Vite toolchain and deliver sizeable production-build performance improvements. Full‑stack teams should prioritize disciplined smoke testing (builds, plugins, runtime behavior, CI) now so they can safely adopt Rolldown when it reaches stable release. (voidzero.dev)

Source:

Source

• Source