Astro is not yet publicly documented or open for code review — it remains an in-progress idea — but a video of Fred demonstrating it to Feross is available.

The case for the approach

Two ideas underpin the project, and both hold up well. First, the Jamstack model is sound: pages that are pre-rendered, static and ship minimal or no JavaScript are a smart default. Second, components are the right abstraction for building interfaces, and JavaScript currently does them best thanks to ES Modules, template literals, web components and mature tooling.

The closest comparison is Eleventy, with one difference: Eleventy's templating languages are less appealing than authoring in JavaScript components.

How Astro works

  • File format. Where Vue uses .vue and Svelte uses .svelte, Astro uses .astro files in a format of their own. JavaScript is enforced at the top of the file in a Frontmatter-like block.
  • Wrapper, not replacement. Astro sits on top of existing libraries rather than replacing them. React and JSX components, Vue files and Svelte files all work, including each library's own state management, and are pulled in with import inside an Astro file.
  • Routing. The filesystem is the default router, as in Next.
  • Styling. CSS is scoped by default, comparable to Vue's <style scoped>. CSS Modules are unnecessary because the benefits are already there.
  • Payload. No JavaScript reaches the front end unless explicitly opted into, or unless the :visible syntax is used, which injects just enough script to lazy load more on demand.
  • Islands. The framework embraces Islands Architecture: most sites are static content with only portions that are interactive or dynamic.
  • Visibility-gated hydration. Requesting JavaScript for an interactive component only once it is visible (via IntersectionObserver) is a first-class feature — effectively loading="lazy" for anything interactive.
  • Content authoring. MDX or similar is included, so content can be written in Markdown while still embedding <Components />.
  • Lineage. Marko, the HTML/JavaScript hybrid language, is credited on the homepage for "asking the question." The approach recalls Alpine and htmx.

Attitude toward prior art

The project avoids the "new thing good, old thing bad" framing. Its stance is closer to taking every good idea from what came before and leaning on what the native web does best — which maps onto Baldur Bjarnason's distinction between kinds of novelty-seeking web developers.

The pattern worth avoiding:

This is the first kind of novelty-seeking web developer. The type that sees history only as a litany of mistakes and that new things must be good because they are new. Why would anybody make a new thing unless it was an improvement on the status quo? Ergo, it must be an improvement on the status quo.

The preferable pattern:

This is the other kind of novelty-seeking web developer, one who seeks to build on the history and nature of the web instead of trying to transform it.