Astro 7.3.8 Drops Direct esbuild Dependency for Vite's Oxc and Rolldown as create-astro Stops Pre-Approving Package Build Scripts

Overview

Astro 7.3.8 and a set of companion packages published on October 8 remove the framework’s direct dependency on esbuild. According to the Astro 7.3.8 release notes, the release changes its internal bundling and code transforms “to use Vite’s Oxc-based transformWithOxc and Rolldown instead of esbuild,” and the notes state that “These packages no longer depend on esbuild directly.” The same change also led the project to stop writing install-script approvals into newly generated projects.

What Changed

The work landed in a single pull request, #18263, titled “Replace esbuild with Vite and Rolldown APIs”, authored by florian-lefebvre. Its description breaks the migration down by package:

• The core astro package uses transformWithOxc for environment-variable replacement and Rolldown for bundling client directives.
• @astrojs/netlify, @astrojs/vercel and @astrojs/markdoc now bundle with Rolldown.
• astro-scripts and astro-vscode build with Rolldown.
• create-astro no longer writes allowScripts or allowBuilds, and the example projects drop their stale entries.

GitHub lists the pull request as touching 63 files with 709 additions and 858 deletions. The description also carries the line “Made with AI” and says the full CI build (pnpm run build:ci) and the affected unit and integration suites pass. The identical refactoring note appears in the release notes for @astrojs/vercel 11.0.13, @astrojs/markdoc 2.0.11 and astro-vscode 2.17.2, which were all tagged on October 8.

The Install-Script Change

The companion create-astro 5.2.6 release removes “the automatic allowScripts and allowBuilds pre-approval from generated projects.” Its stated reason is that “Astro’s dependencies no longer run install scripts, so the workaround is no longer needed.” The release notes do not name the package that previously required the approval.

Separately, 7.3.8 includes a fix so that astro add no longer removes existing allowBuilds approvals from pnpm-workspace.yaml with pnpm v11.0 to v11.22. The release also fixes Astro.cache being undefined when a custom 404 or 500 page is rendered by the error handler, and a glob() loader bug where changed files were not reloaded in development when the pattern began with an extglob such as !(drafts)/**/*.md.

Context

The move follows the bundler changes upstream in Vite. As previously reported, Vite 8 replaced its dual esbuild-and-Rollup architecture with Rolldown. Astro’s release notes describe the new code paths as using Vite’s own Oxc-based transform and Rolldown, which means the framework now leans on the toolchain Vite already ships rather than carrying a separate esbuild copy. The sources do not frame it that way explicitly, so that reading is an interpretation of the changes listed above.

The 7.3.8 release arrived a day after Astro 7.3.7, which was published on October 7.

What We Don’t Know

• The release notes and pull request description do not report build-time, install-size or output differences from the migration, so any performance effect is unquantified.
• It is not stated whether user projects that import esbuild themselves, or that rely on esbuild-specific behavior in custom integrations, are affected. The notes only say that the listed Astro packages no longer depend on esbuild directly.
• The pull request description does not say which parts of the change were generated with AI assistance beyond the “Made with AI” line.
• The line count and file count come from the pull request page and were not independently audited.