Julia Evans documented her attempt to move a Vue project from a plain <script src="script.js"> setup to a real build step, and landed on esbuild as a middle ground between no tooling and full frameworks. Her usual approach, as she describes it, is an index.html plus a script.js loaded with a script tag and nothing else.

Why a bundler at all

The pull toward modern tooling came from wanting access to npm. The import style she wanted to use is not valid ES module syntax, so it effectively requires npm plus a bundler. Historically that meant webpack, rollup, or Parcel; more recently it points toward Vite. Julia ruled out the heavier options on confidence grounds, saying she did not understand what vue-cli-service and vite were doing and would rather keep a setup she could fix herself.

esbuild sits a rung lower on the complexity ladder. Vite itself relies on esbuild for part of its work — specifically dependency pre-bundling in place of Rollup, which the Vite docs credit with significant gains in cold server start and re-bundling on dependency invalidation.

The Vue resolution snag

The setup nearly worked cleanly. The problem was which copy of Vue esbuild resolved from import Vue from 'vue';: it picked vue.runtime.esm.js, the browser-oriented runtime build that ships without the compiler. Julia worked through it, and her verdict was that esbuild felt more approachable and transparent than the webpack-based tools she had used before, even without fully understanding everything it does.

The no-build alternative

The episode is also an argument for services like Skypack, which let you write modern import statements against Vue in the browser without any build process at all.