Astro 7.0
The major release of astro (June 22, 2026). Two things stand out: a Rust-powered speed overhaul that closes much of Astro’s old build-speed deficit, and a set of full-stack features (request pipeline, route caching, edge CDN) that push it further across the SSG→meta-framework boundary.
Speed — the Rust rewrite
Builds are 15–61% faster, from a stack of changes:
- The
.astrocompiler moved from Go to Rust. - Markdown/MDX now runs through a new engine (“Sätteri”).
- Rendering uses a queue-based strategy.
- Bundling rides Vite 8’s Rolldown (the Rust bundler Astro cites as “10–30× faster than Rollup”).
This matters for the wiki’s standing “two distinct fasts” split: Astro had conceded build speed to eleventy/hugo/zola while winning runtime core-web-vitals. Astro 7 narrows the build gap by adopting the same Rust/single-fast-binary lever those tools use, rather than staying a pure-Node toolchain.
Full-stack features
- Request pipeline — a new
src/fetch.tsentrypoint gives full control over requests via standard fetch-handler patterns; supports frameworks like Hono, so middleware (e.g. auth) can compose before type-safe Actions, fixing an earlier ordering limit. - Route caching (now stable) — a platform-agnostic
Astro.cacheAPI for on-demand-rendered responses, plus experimental CDN providers (Netlify, Vercel, Cloudflare) that push cache directives to the edge, and automatic cache management tied to live content collections. - AI/agent dev support —
astro dev --backgroundspawns managed background dev processes with automatic agent detection, structured JSON logging, and a health endpoint at/_astro/status.
Breaking changes — stricter HTML
The Rust compiler drops browser-style HTML repair for predictable, explicit behavior:
- No silent HTML correction (tags are no longer reordered).
- JSX-style strictness — tags must be properly closed.
- JSX whitespace handling collapses newlines between inline elements.
Why it matters here
Astro 7 is direct evidence on the spoke’s open “is SSG still a coherent category?” question. The
src/fetch.ts pipeline, stable route caching, and edge-CDN directives are meta-framework / full-stack
capabilities — the announcement explicitly frames Astro as moving “from a static site generator toward a
full-stack framework.” So the very tool this wiki treats as its central SSG keeps extending into
per-request territory (after astro-server-islands did so for rendering), sharpening the boundary the
wiki scoped around when it ruled React meta-frameworks (Next.js/Gatsby/Remix) out. The reflexive note:
the agent-detection + JSON-logging dev features are aimed at exactly the case this hub is — an agent
maintaining an Astro site (the site/ build).
Caveats
A first-party release announcement (T1 for what shipped), so the performance numbers (15–61%, “10–30×”) are vendor-reported, not independently benchmarked. Dated snapshot; version facts go stale.
Related
astro · astro-server-islands · static-site-generator · eleventy · zola · hugo · islands-architecture · netlify · core-web-vitals