lead · github
esbuild: The bundler that actually keeps pace with your dev loop
Written in Go instead of JavaScript, esbuild cuts bundling time by 10–50x. For web builders shipping products, that means faster feedback loops and measurably shorter CI/CD runs.
evanw/esbuild ↗A bundler takes your JavaScript modules, CSS, and assets, stitches them together, and spits out optimized files browsers can load fast. Most bundlers (webpack, Parcel) do this in JavaScript, which gets slow as your codebase grows. esbuild rewrote the whole thing in Go—a compiled language—so bundling that took 30 seconds now takes under a second. You don't interact with it directly; your build tool (Vite, Next.js, Remix) uses it under the hood. The payoff: tighter dev loops, faster CI feedback, less time waiting for builds. If you're shipping web products, you're already benefiting from it. If you're building your own tooling, it's the speed benchmark everything else competes against.
Share kit
esbuild: Why your bundler shouldn't make you wait
Go-powered bundling cuts 30-second builds down to under 1 second. Most modern web tools (Vite, Next.js, Remix) use it by default. If you're hand-rolling builds or stuck on older tooling, it's worth the swap for dev velocity alone.
esbuild: written in Go, not JavaScript. Bundling that used to take 30s now takes <1s. You probably use it already (Vite, Next.js, Remix all rely on it). If you don't—your CI/CD will thank you for the switch. https://github.com/evanw/esbuild
The bundler that doesn't waste your time. esbuild's Go rewrite delivers 10–50x speed gains over JavaScript-based alternatives—which directly cuts dev loop friction and CI/CD wait time. Whether you're optimizing for developer experience or shipping lean, it's now table-stakes infrastructure. https://github.com/evanw/esbuild
just shipped a feature that needed bundling 50x faster than our old setup. swapped webpack for esbuild and watched our CI/CD time collapse from 8 minutes to under a minute. not exaggerating—the Go rewrite actually matters when you're iterating hard. if you're building web products and your dev loop feels like molasses, this is table-stakes now. the speed isn't a nice-to-have; it's friction you can actually measure in your deploy pipeline. github.com/evanw/esbuild
esbuild changed how we think about bundler speed. went from webpack → esbuild and cut our CI/CD by 87%. not hype; just math. if you're shipping web and care about iteration velocity, this is the move.