Astro 7.0: Rust Compiler, Vite 8, and Up to 61% Faster Builds

Astro 7.0 shipped on July 7, 2026, and the release is all about speed. The framework rewrote its .astro compiler in Rust, upgraded to Vite 8 with the new Rolldown bundler, and introduced a faster rendering engine - resulting in build times that are 15-61% faster across their benchmarks.

What Changed

The performance story has three parts:

Rust-based .astro Compiler. The parser and transformer that handles .astro files is now written in Rust. This isn't just a port - the new compiler enforces stricter HTML parsing rules, which is both a feature and a breaking change.

Vite 8 and Rolldown. The biggest upstream change is Vite 8, which ships Rolldown - a Rust-based bundler that replaces both esbuild (for dev) and Rollup (for production) with a single unified tool. Rolldown is 10-30x faster than Rollup in benchmarks while maintaining API compatibility with existing Rollup plugins.

Satteri Markdown Pipeline. Markdown and MDX processing now runs through Satteri, a new Rust-powered pipeline that replaces the remark/rehype JavaScript stack. This is particularly impactful for documentation sites and blogs with hundreds or thousands of markdown files.

Queued Rendering Engine. The internal rendering system has been replaced with a queue-based approach that's approximately 2.4x faster according to their benchmarks.

Breaking Changes Worth Knowing

The Rust compiler is stricter about HTML. Tags must be properly closed, and attributes must be properly terminated. The old JavaScript compiler would silently fix these issues; the new one throws errors.

<!-- This now fails -->
<div>
  <p>Unclosed paragraph
</div>

<!-- This works -->
<div>
  <p>Properly closed paragraph</p>
</div>

Whitespace handling also changed. Newlines between inline elements no longer produce visible spaces, following JSX conventions:

<!-- In Astro 6: produces "Hello World" with a space -->
<!-- In Astro 7: produces "HelloWorld" -->
<span>Hello</span>
<span>World</span>

What HN is Saying

The Hacker News discussion has 35 comments with a mix of reactions.

On the Rust rewrite. One commenter joked about "awaiting the rewrite to assembly," but the response from Princesseuh (who built the Rust compiler and Satteri) was informative: "Crossing data between Rust and JS is inherently kinda slow (relatively), so there's a constant push and pull between flexibility and performance that's not always easy to reason about."

On the strict HTML enforcement. This is the most debated change. One developer noted it "actively prevents upgrading sites which need to deal with remote content that is not written in strict HTML." The Astro team clarified this only affects .astro files - remote HTML loaded via set:html isn't affected.

On version velocity. Multiple commenters noted Astro 7 arrived shortly after Astro 6, leading to upgrade fatigue. The team explained this was timing - Vite 8/Rolldown shipped right after Astro 6, and Vite major versions typically require an Astro major version due to deep integration.

On actual performance gains. Not everyone saw improvements. Cassidy Williams (Astro's Head of Developer Experience) shared: "I upgraded my website recently and it's exciting! That being said, I admit my builds didn't get faster (they actually on average slowed down a bit)." The Astro team responded that performance gains are most visible on larger sites with thousands of pages, especially those using MDX.

On AI developer support. Astro 7 added features specifically for AI coding agents: a background dev server mode (astro dev --background) with automatic agent detection, structured JSON logging, and a health endpoint at /_astro/status. One commenter called this "a good model" for how frameworks should support agent workflows.

The Dependency Story

An underappreciated change: Astro's dependency count dropped from 247 packages in v6 to 190 in v7. The unified ecosystem (remark, rehype, and their plugins) contributed a significant portion of the old count. Satteri consolidates much of this while maintaining the same AST format for plugin compatibility.

Migration

The upgrade path is straightforward for most projects:

npx @astrojs/upgrade

The automated upgrade handles most migrations. The main manual work is fixing any strict HTML violations in .astro files - the compiler errors will point you to the specific issues.

Why This Matters

Astro has positioned itself as the default choice for content-heavy sites - marketing pages, documentation, blogs - where you want server-rendered HTML with minimal client JavaScript. The 7.0 release reinforces that position.

The Rust investments are paying off. The JavaScript ecosystem has been trending toward Rust tooling for years (swc, esbuild, Rolldown, oxc, biome), and Astro is now part of that movement rather than just benefiting from it.

The AI developer support is also notable. Frameworks don't typically ship first-party features for agent workflows, but Astro is betting that "Claude Code + Astro" will be a common stack for quickly building sites.

Sources

• Astro 7.0 Release Blog
• Hacker News Discussion
• Satteri Documentation
• Vite 8 Announcement