Why data fetching happens at build time in Astro - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to fetch data at build time in Astro.

Astro

export async function getStaticPaths() {
  const response = await fetch([1]);
  const data = await response.json();
  return { paths: data.map(item => ({ params: { id: item.id } })), fallback: false };
}

Drag options to blanks, or click blank then click option'

A'https://api.example.com/data'

Bimport data from './data.json'

Cconsole.log('fetch')

D42

Attempts:

3 left

💡 Hint

Common Mistakes

Using a number instead of a URL string

Trying to import data instead of fetching it

The fetch function needs a URL string to get data from an API at build time.

2fill in blank

medium

Complete the code to return static props with fetched data in Astro.

Astro

export async function getStaticProps() {
  const res = await fetch('https://api.example.com/items');
  const items = await res.json();
  return { props: { [1] } };
}

Drag options to blanks, or click blank then click option'

Aresponse

Bdata

Citems

Dresult

Attempts:

3 left

💡 Hint

Common Mistakes

Returning a variable that was not defined

Using the wrong variable name

The fetched JSON data is stored in items, which should be returned as props.

3fill in blank

hard

Fix the error in the Astro component to use fetched data correctly.

Astro

---
const { [1] } = Astro.props;
---
<h1>Item List</h1>
<ul>
  {items.map(item => <li>{item.name}</li>)}
</ul>

Drag options to blanks, or click blank then click option'

Aitems

Bdata

Cprops

Dresponse

Attempts:

3 left

💡 Hint

Common Mistakes

Destructuring the wrong variable name

Using a variable not passed as prop

The component expects items from props to render the list.

4fill in blank

hard

Fill both blanks to create a static page with data fetched at build time.

Astro

export async function getStaticProps() {
  const res = await fetch([1]);
  const data = await res.json();
  return { props: { [2] } };
}

Drag options to blanks, or click blank then click option'

A'https://api.example.com/posts'

Bitems

Cdata

D'https://api.example.com/users'

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing URLs and variable names

Returning wrong variable as props

The URL to fetch posts is needed, and the JSON data variable data should be returned as props.

5fill in blank

hard

Fill all three blanks to fetch data and render it in Astro component.

Astro

---
const { [1] } = Astro.props;
---
<h2>Users</h2>
<ul>
  { [2].map(user => <li key={user.id}>{user.[3]</li>)}
</ul>

Drag options to blanks, or click blank then click option'

Ausers

Cname

Did

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong variable names

Accessing a property that doesn't exist

The component destructures users from props, maps over it, and displays each user's name.

Practice

1. Why does Astro fetch data at build time instead of on every user request?

easy

A. To make pages load faster by preloading content

B. To reduce the size of the website files

C. To allow users to edit content directly on the page

D. To prevent search engines from indexing the site

Solution

1. Step 1: Understand build time data fetching

   Astro fetches data once during build, so pages have content ready before users visit.

2. Step 2: Connect build time fetching to page speed

   Since content is preloaded, pages load faster for users without waiting for data requests.

3. Final Answer:

   To make pages load faster by preloading content -> Option A

4. Quick Check:

   Build time fetching = faster page load [OK]

Hint: Build time fetching means content is ready before user visits [OK]

Common Mistakes:

• Thinking data fetching happens on every user request
• Confusing build time with runtime fetching
• Believing it reduces file size directly
• Assuming it blocks search engine indexing

2. Which of the following is the correct way to fetch data at build time in an Astro component?

easy

A. Use fetch() inside the component's render() function

B. Use Astro.fetchContent() inside getStaticPaths()

C. Use export async function getStaticProps() to fetch data

D. Use export async function getStaticPaths() to fetch data

Solution

1. Step 1: Identify Astro's build time data fetching method

   Astro uses getStaticPaths() to fetch data at build time for generating pages.

2. Step 2: Differentiate from other frameworks

   getStaticProps() is from Next.js, not Astro; fetch() inside render runs at runtime, not build time.

3. Final Answer:

   Use export async function getStaticPaths() to fetch data -> Option D

4. Quick Check:

   Astro build time fetch = getStaticPaths() [OK]

Hint: Astro uses getStaticPaths() for build time data fetching [OK]

Common Mistakes:

• Using getStaticProps() which is Next.js specific
• Fetching data inside render causing runtime fetch
• Confusing fetchContent() as a standard method
• Not exporting the function properly

3. Given this Astro code snippet, what will be the output when the site is built?

export async function getStaticPaths() {
  return [{ params: { id: '1' } }, { params: { id: '2' } }];
}

const data = { '1': 'Apple', '2': 'Banana' };

export default function Page({ params }) {
  return 
{data[params.id]}
;
}

medium

A. Apple and Banana pages generated at build time

B. Only Apple page generated, Banana missing

C. Runtime error because data is not fetched inside the component

D. Empty pages because data is undefined

Solution

1. Step 1: Understand getStaticPaths output

   It returns two paths with ids '1' and '2', so two pages will be built.

2. Step 2: Check data usage in component

   Component uses params.id to get data from the object, so 'Apple' and 'Banana' will render correctly.

3. Final Answer:

   <p>Apple</p> and <p>Banana</p> pages generated at build time -> Option A

4. Quick Check:

   getStaticPaths creates pages for each id [OK]

Hint: getStaticPaths creates pages for each param at build time [OK]

Common Mistakes:

• Assuming only one page is generated
• Thinking data must be fetched inside component
• Confusing build time with runtime data fetching
• Believing data object is undefined

4. What is wrong with this Astro build time data fetching code?

export async function getStaticPaths() {
  const response = await fetch('https://api.example.com/items');
  const items = await response.json();
  return items.map(item => ({ params: { id: item.id } }));
}

export default function Page({ params }) {
  return 
{params.id}
;
}

medium

A. Fetching data inside getStaticPaths is not allowed

B. getStaticPaths must return an object with a 'paths' key

C. Component cannot access params in Astro

D. Missing async keyword on the component function

Solution

1. Step 1: Check getStaticPaths return format

   Astro expects getStaticPaths to return an object with a 'paths' array, not just an array.

2. Step 2: Identify correct return structure

   The correct return is { paths: [...] }, so returning only the array causes an error.

3. Final Answer:

   getStaticPaths must return an object with a 'paths' key -> Option B

4. Quick Check:

   getStaticPaths return = { paths: [...] } [OK]

Hint: getStaticPaths must return { paths: [...] } object [OK]

Common Mistakes:

• Returning array directly instead of object
• Thinking fetch is disallowed in getStaticPaths
• Assuming params are inaccessible in component
• Forgetting async on component (not required)

5. You want to build a blog with mostly static posts but occasionally updated content. Why is fetching data at build time the best choice in Astro for this scenario?

hard

A. Because it prevents any data from being cached, ensuring fresh content always

B. Because it allows the blog to update instantly on every user visit

C. Because it preloads content for fast page loads and good SEO, suitable for mostly static posts

D. Because it requires no code to fetch data, making development faster

Solution

1. Step 1: Understand the nature of mostly static content

   Posts that change rarely benefit from preloading data at build time for speed and SEO.

2. Step 2: Match build time fetching benefits to blog needs

   Preloading content means pages load quickly and search engines see full content, ideal for mostly static blogs.

3. Final Answer:

   Because it preloads content for fast page loads and good SEO, suitable for mostly static posts -> Option C

4. Quick Check:

   Mostly static content = build time fetch for speed & SEO [OK]

Hint: Mostly static content? Use build time fetch for speed and SEO [OK]

Common Mistakes:

• Thinking build time fetch updates instantly on every visit
• Believing it disables caching completely
• Assuming no code is needed to fetch data
• Confusing build time with runtime fetching