From d0465eef237c38c6b9276e2e47746c3353f7a617 Mon Sep 17 00:00:00 2001 From: patak Date: Thu, 16 Nov 2023 09:57:56 +0100 Subject: [PATCH] docs: improve why not bundle with esbuild (#14998) --- docs/guide/why.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guide/why.md b/docs/guide/why.md index d58d165ca0228e..0169e02907a77c 100644 --- a/docs/guide/why.md +++ b/docs/guide/why.md @@ -53,7 +53,7 @@ Ensuring optimal output and behavioral consistency between the dev server and th Vite's current plugin API isn't compatible with using `esbuild` as a bundler. In spite of `esbuild` being faster, Vite's adoption of Rollup's flexible plugin API and infrastructure heavily contributed to its success in the ecosystem. For the time being, we believe that Rollup offers a better performance-vs-flexibility tradeoff. -That said, `esbuild` has progressed a lot in the past years, and we won't rule out the possibility of using `esbuild` for production builds in the future. We will keep taking advantage of new capabilities as they are released, as we have done with JS and CSS minification where `esbuild` allowed Vite to get a performance boost while avoiding disruption for its ecosystem. +Rollup has also been working on performance improvements, [switching its parser to SWC in v4](https://github.com/rollup/rollup/pull/5073). And there is an ongoing effort to build a Rust-port of Rollup called Rolldown. Once Rolldown is ready, it could replace both Rollup and esbuild in Vite, improving build performance significantly and removing inconsistencies between development and build. You can watch [Evan You's ViteConf 2023 keynote for more details](https://youtu.be/hrdwQHoAp0M). ## How is Vite Different from X?