Kelvin O Omereshone

Developer. Teacher. Speaker.

← Back to blog

Last updated on

Understanding Astro components

After rewriting my website with Astro, I was impressed by Astro components and how easy it was for me to learn enough of its syntax and conventions to be productive. In this article, I’ll give you a crash course on Astro components.

The need for componentization

I believe one of the reasons frameworks like Vue, React, and Svelte have been super popular in the JavaScript frontend space is components.

I know this because as a developer myself, I have enjoyed writing components and following a component-driven paradigm for building websites.

These frameworks have been super appealing for building UIs on the web and in the JavaScript space, writing components is sort of a household concept at this point.

So it’s only logical for a framework like Astro seeking to be an alternative school of thought for building content-based websites to have a component syntax of its own at its core and I believe it executed this perfectly.

What is an Astro component?

An Astro component is a file ending with a .astro extension.

If you are familiar with a .vue file for Vue or a .jsx file for React, an Astro component is similar to these other SPA-focused frameworks components but with a notable difference which we will look at in a bit.

So whenever you are in an Astro codebase, you will typically find Astro components inside the components/, layouts/ and pages/ folders.

The usage of an Astro component

If you speak frontend frameworks, the usage of an Astro component might be easy to infer. However, let’s go over them.

In Astro, an Astro component can be used for either of these reasons.


Remember I mentioned Astro components have a notable difference from frameworks like Vue, React, or Svelte components? Yeah and this is the difference…

Unlike these other frameworks, Astro components don’t have a client runtime and it renders to HTML at build time.

“What does this mean?”, you may ask, well, it means that Astro components output HTML during build time in Node.js and this HTML is what it’s being sent to the client when you visit a page.

This is a difference worth mentioning because you might not fully grasp the implication of this if you are coming from a SPA-based framework.

For example, since Astro allows you to have Vue, React, and Svelte components in Astro components, you may think these components you’ve imported will work as they do in their respective frameworks but then you click a button component and you didn’t get the expected behavior because Astro renders them to HTML only at build time(although there are ways to hydrate interactive components).

Understand: Astro components are HTML-only. They are a superset of HTML and as such you get HTML in the client by default.

To put it simply: The output of an Astro component after it is built is HTML by default.

Inside an Astro component

Let’s step into an Astro component and see what it is made of. Below is the basic structure of an Astro component:

// Component Script (JavaScript/TypeScript)

<!-- Component Template (HTML + JS Expressions) -->

Let’s take a look at these two sections of an Astro component separately.

Component Script

Within ---(code fences) is where you author JavaScript(and TypeScript). Variables in this section are available by default in the Component Template. If you are familiar with Frontmatter then the --- code fence will be familiar.

One thing I love about the Component Script is that with zero setup and configuration, you can author TypeScript by default.

I think this is cool as the TypeScript setup is one of the reasons I don’t use it often in my project but in Astro I find myself writing TypeScript and it does feel good.

Here are a couple of things you’d want to do in the Component Script:

Import other components

import HeaderLink from './HeaderLink.astro'
// ...

Define component props

// ...
export interface Session {
  title: string
  teacher: string
  teacherUrl: string
  date: string
  poster: string
  url?: string
export interface Props {
  session: Session
const { session } = Astro.props
// ...

Notice that I am using TypeScript for validating component props. That’s sweet.

Variables and business logic

Any valid non-client side JavaScript is valid within the Component Script. Emphasis on non-client side JavaScript. Recall these components will be executed at build time in Node.js so you don’t have access to document or window and generally the DOM. Here is an example of some business logic going on in the Component Script:

// Use Astro.glob() to fetch all posts,
// filter out draft posts and sort them by date.
const posts = (await Astro.glob('./blog/*.{md,mdx}'))
  .filter((post) => !post.frontmatter.draft)
    (a, b) =>
      new Date(b.frontmatter.pubDate).valueOf() -
      new Date(a.frontmatter.pubDate).valueOf()

Component Template

An Astro component is made up of good ol’ HTML and optionally JavaScript expressions inspired by JSX for things like interpolation, conditional rendering, loops, etc.

Let’s look at an example combining both Component Script and Component Template

import SocialLink from './SocialLink.astro'
import socials from '../socials.json'

<ul class="flex items-center space-x-2">
  { => (
      <SocialLink link={} icon={social.icon} title={social.title} />

You can see like in JSX, I can use the built-in array map method on an Array-like object to dynamically create markup.

Also, notice interpolation is done via {} just like in JSX.

Difference between Astro components and JSX

Even though Astro components are inspired JSX for things like interpolation and dynamic rendering, they differ in 2 significant ways. Let’s take a look.


This is a big one for me because I didn’t like having className replace the HTML class attribute in JSX. Astro took care of this so you can use class attributes inside Astro components.

<ul class="flex items-center space-x-2"></ul>


Unlike in JSX, HTML comments are valid inside Astro components.

<!-- A valid HTML comment syntax is a .astro file -->


Astro components improve the DX of writing MPAs as we have been so used to doing in SPA frameworks like Vue, React, or Svelte. In this article, we took a high-level look at Astro components, and how it is both similar and different from other frameworks’ components.