Astro 7's Rust compiler promises 15–61% faster builds. One developer's got slower.

Inside the rewrite: a new compiler and a homemade markdown engine

Astro 7.0 is a plumbing release, and the plumbing is now mostly Rust. The headline payoff is build time. On an M4 Pro, the team's own benchmark suite:

The second big change is invisible until it breaks something. Astro dropped the unified/remark/rehype markdown stack for a homegrown Rust processor called Sätteri (pulldown-cmark for CommonMark, Oxc for MDX), pulling GFM, math, heading IDs, smart punctuation and wikilinks into the core. The rewritten compiler also stops silently repairing your HTML: unclosed tags and unterminated attributes now throw errors, and whitespace between inline elements collapses JSX-style. Rounding out the release: a Hono-compatible request pipeline via a new src/fetch.ts, stable route caching, and an AI mode where astro dev runs in the background and emits structured JSON logs, which the team calls the most-upvoted request on its roadmap.

The upgrade tax nobody advertised

The Rust rewrite came with a stricter compiler, and that is where the first complaints landed. Astro no longer auto-corrects your markup, which is a problem when the markup isn't yours to fix.

"The switch to strict HTML compilation is just not cool, and actively prevents upgrading sites which need to deal with remote content that is not written in strict HTML." — a developer with remote content to render

The markdown swap drew the same worry from the other direction: leaving the rehype ecosystem behind for speed.

"Switch from widely supported unified/rehype to own rehype-incompatible markdown tooling just for build time speed improvement is quite upsetting. Good that they added a tool to keep using rehype, but I'm unsure that it will last." — a developer relying on rehype plugins

The engineer who wrote it is answering questions

The author of the new pipeline showed up to take the hits directly:

"I made the Rust compiler and the Rust Markdown pipeline in this, let me know if you have any questions, glad to answer anything!" — the engineer who built Astro 7's Rust compiler and Sätteri

Not every number moved the promised way. One developer's upgrade cut against the headline:

"I upgraded my website recently and it's exciting! That being said… my builds didn't get faster (they actually on average slowed down a bit)." — a developer whose own upgrade slowed builds

A quieter win landed better: the dependency count fell from 247 in v6 to 190 in v7, which a developer who tracked the counts welcomed as the JS ecosystem finally shedding weight.

"Does v7 mean seven breaking changes?"

Under the features sat a recurring unease about Astro's pace. Each major is faster to build and arrives with a migration.

"Does v7 mean that there have been 7 breaking changes thus far? So if I started my project on v1, I had to revise it 6 times to date? If yes, then this instability is a serious concern to me." — a developer weighing whether to adopt it

Another had just finished moving to Astro 6 when 7 landed. If you maintain an Astro site, that is the real line item this release adds: the build is quicker, and you will pay for it again at the next major.