SYSTEM Cited by 1 source

esbuild

esbuild (esbuild.github.io) is an extremely fast JavaScript / TypeScript bundler written in Go. Positioned for server-side bundling workloads and SDK build phases where Rollup's plugin ecosystem isn't needed and raw build speed is.

Stub

This page covers only what currently-ingested sources name about esbuild. Broader esbuild internals (plugin API, bundler output shapes, transform API vs build API, tree-shaking model) are out of scope until a source discusses them.

Relevance to the wiki (2026-04-21)

Vercel's 2026-04-21 WDK post names esbuild as the server-side bundler in its integration pipeline:

• Step mode + Workflow mode bundles are emitted by WDK's esbuild-driven build phase (separate from the user's framework bundler). Per the SWC three-mode-transform pattern: "Step mode runs during WDK's esbuild phase." + "Workflow mode also runs during esbuild."
• Nitro-shimmed integration for Express/Hono also runs esbuild under Nitro's build system.
• HMR rebuilds triggered by Vite's hotUpdate hook via vite-hotupdate-directive-triggered-rebuild invoke WDK's esbuild builder.build().

esbuild runs in parallel to the user's framework bundler (Rollup in the Vite-based case): client-mode code goes through Rollup during the framework build, step-mode and workflow-mode code goes through esbuild during WDK's own build phase. The two output streams don't interfere.

Why esbuild (rather than Rollup) for server-side

Not explicitly disclosed in the 2026-04-21 post. Plausible reasons (per general ecosystem norms):

• Faster build times (esbuild is ~10-100× faster than Rollup).
• Smaller plugin surface needed for server bundling (handler code, no CSS / asset pipeline).
• Nitro uses esbuild internally — shared build substrate.

Seen in

• sources/2026-04-21-vercel-inside-workflow-devkit-how-framework-integrations-work — canonical wiki introduction. esbuild is WDK's server-side bundler for step + workflow handler outputs; Nitro uses esbuild as its internal bundler for the bundlerless-framework shim.

Related

• systems/nitro-unjs — uses esbuild internally.
• systems/vite — sibling build tool; Vite uses esbuild for dev-server dep pre-bundling but Rollup (or Rolldown) for production.
• systems/rollup — sibling bundler; Rollup is client- side in the WDK Vite-based integration, esbuild is server-side.
• systems/vercel-workflow — the 2026-04-21 canonical instance.
• swc-plugin-three-mode-transform — the mode- parameterised plugin invokes esbuild for step + workflow modes.
• virtual-handler-via-nitro-for-bundlerless-frameworks — the shim pattern that uses esbuild.
• vite-hotupdate-directive-triggered-rebuild — HMR integration that triggers esbuild rebuilds.