Article

Astro 6.1: Sharper Image Defaults and Smoother View Transitions

Astro 6.1 sets Sharp codec defaults once in config, skips redundant view-transition animations on mobile, and exposes i18n fallback routes to integrations.

Editorial Team EN

Astro 6.1 reads like a cleanup list, and that is the appeal. It picks off papercuts left over from the 6.0 jump: image codec defaults you had to repeat on every call, a view-transition flicker on phones, and integrations blind to i18n fallbacks. Six fixes and one ergonomic win, none of which forces an upgrade.

Sharp codec defaults you set once

Image quality settings used to be a per-call chore. A specific encoder behavior had to be carried through every image, and a missed one shipped at the wrong quality. Astro 6.1 lets you set codec-specific Sharp defaults once in config; they apply to every image at build. The default is correct by construction instead of correct only where you remembered to type it.

Typography and i18n for real audiences

Per-transformation SmartyPants

SmartyPants converts straight quotes and hyphens into typographic ones, and its defaults assume English. That is wrong for a German or French reader, where quote marks and dashes follow different rules. Astro 6.1 adds advanced markdown SmartyPants configuration so you control punctuation per transformation, picking language-specific quotes and dashes. The Markdown configuration docs cover where these options sit.

Fallback routes for integration authors

Astro 6.1 exposes fallbackRoutes on every route in the astro:routes:resolved hook. An integration can see which locales a given route falls back to, instead of guessing from the i18n config or rebuilding that resolution itself. Sitemap and SEO tooling benefit directly.

A calmer client router on mobile

View transitions had an ugly edge on phones. When a mobile browser ran its own visual transition for a navigation, the client router ran one too, stacking two animations on the same swipe. Now the client router skips its animation when the browser supplies a transition, so the native gesture wins and the double-flicker is gone.

Guardrails: Vite 8, React, reverse proxies

The Vite 8 change is a warning, not a feature. If Astro detects Vite 8 on dev start, it warns and auto-adds a version override so the dev server keeps running. You get a heads-up with a safe default already written, instead of a stack trace.

React picks up two hydration fixes: conditional slot rendering and experimentalReactChildren mismatches, both sources of hydration warnings that send you hunting for a server-client divergence that is not yours.

The CSRF fix lands for anyone behind a TLS-terminating proxy. In dev, checkOrigin now reads X-Forwarded-Proto, so a request that arrives as HTTPS at the proxy but HTTP at the app no longer trips a false origin mismatch.

The fixes meet the framework where it already was and remove friction you had learned to route around. For the wider picture, the Astro 6 feature guide tracks every release in this generation, and the Astro topic hub collects the surrounding coverage.

© yippy® 2026 · YIPPY v0.64.1