Incremental builds with data in Astro - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

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

Astro

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

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

Afallback

Bhydrate

Ccache

Drender

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'hydrate' instead of 'fallback' causes build errors.

Confusing 'render' with the fallback behavior.

The fallback property controls whether Astro should generate pages for paths not returned by getStaticPaths. Setting it to false disables fallback pages.

2fill in blank

medium

Complete the code to define a dynamic route parameter in Astro.

Astro

---
const { params } = Astro;
const id = [1];
---

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

AAstro.id

BAstro.params

Cparams.route

Dparams.id

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to access Astro.id directly.

Using params.route which does not exist.

Dynamic route parameters are accessed via params. Here, params.id gets the id from the URL.

3fill in blank

hard

Fix the error in the code to correctly export a data fetching function for incremental builds.

Astro

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

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

AgetStaticProps

BgetServerSideProps

CgetStaticPaths

DgetData

Attempts:

3 left

💡 Hint

Common Mistakes

Using Next.js specific functions like getStaticProps which don't exist in Astro.

Using a non-existent function getData.

In Astro, getStaticPaths is used to fetch data for incremental static generation of pages.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that filters data during build.

Astro

const filteredData = Object.fromEntries(
  Object.entries(data).filter(([key, value]) => value.[1] [2] 10)
);

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

Ascore

B>

C<

Dlength

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'length' instead of 'score' for the property.

Using '<' instead of '>' causing wrong filtering.

This code filters entries where the score is greater than 10.

5fill in blank

hard

Fill all three blanks to create a map of uppercase keys to values filtered by a condition.

Astro

const result = Object.fromEntries(
  Object.entries(data)
    .filter(([[1], [2]]) => [2] > 0)
    .map(([key, value]) => [key.[3](), value])
);

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

Akey

Bvalue

CtoUpperCase

Dlength

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping key and value names.

Using 'length' instead of 'toUpperCase' for the method.

This code filters entries where the value is greater than zero, then maps keys to uppercase.

Practice

1. What is the main benefit of using incremental builds in Astro projects?

easy

A. Only pages with changed data are rebuilt, saving time

B. All pages are rebuilt every time for consistency

C. It disables data fetching during build

D. It automatically deploys the site to a server

Solution

1. Step 1: Understand incremental build purpose

   Incremental builds focus on rebuilding only what changed, not the whole site.

2. Step 2: Identify the benefit in context

   This saves build time and speeds up development and deployment.

3. Final Answer:

   Only pages with changed data are rebuilt, saving time -> Option A

4. Quick Check:

   Incremental builds = rebuild changed pages only [OK]

Hint: Incremental means update only changed parts [OK]

Common Mistakes:

• Thinking all pages rebuild every time
• Confusing incremental builds with disabling data fetching
• Assuming it automatically deploys the site

2. Which Astro function is used to specify which pages should be built incrementally with data?

easy

A. useEffect

B. getServerSideProps

C. renderToString

D. getStaticPaths

Solution

1. Step 1: Recall Astro data fetching functions

   Astro uses getStaticPaths to define dynamic routes for static generation.

2. Step 2: Match function to incremental build role

   getStaticPaths tells Astro which pages to build incrementally with data.

3. Final Answer:

   getStaticPaths -> Option D

4. Quick Check:

   Page list for incremental build = getStaticPaths [OK]

Hint: Use getStaticPaths to list pages for static build [OK]

Common Mistakes:

• Confusing getStaticPaths with getServerSideProps
• Using React hooks like useEffect in Astro build functions
• Thinking renderToString controls incremental builds

3. Given this Astro code snippet, what will be the output for the page paths?

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

medium

A. No pages will be built because return type is wrong

B. Only page /1 will be built

C. Pages for /1 and /2 will be built incrementally

D. Pages for /id/1 and /id/2 will be built

Solution

1. Step 1: Analyze getStaticPaths return value

   The function returns an array with params objects containing id '1' and '2'.

2. Step 2: Understand path generation

   Astro uses these params to build pages at /1 and /2 paths incrementally.

3. Final Answer:

   Pages for /1 and /2 will be built incrementally -> Option C

4. Quick Check:

   Params id '1' and '2' create /1 and /2 pages [OK]

Hint: Params define page paths directly [OK]

Common Mistakes:

• Assuming only first param builds a page
• Thinking return type must be an object, not array
• Confusing path format with nested folders

4. Identify the error in this Astro incremental build code snippet:

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

medium

A. getStaticPaths must return an array, not an object

B. Params should be a string, not an array

C. Function must be synchronous, not async

D. Return value should be a function, not an object

Solution

1. Step 1: Check getStaticPaths return type

   Astro expects getStaticPaths to return an array of params objects, not an object wrapping an array.

2. Step 2: Identify correct return structure

   The code incorrectly returns an object with params array instead of just the array.

3. Final Answer:

   getStaticPaths must return an array, not an object -> Option A

4. Quick Check:

   Return type must be array for getStaticPaths [OK]

Hint: Return array directly from getStaticPaths [OK]

Common Mistakes:

• Wrapping params array inside an object
• Making function synchronous when async is allowed
• Returning a function instead of data

5. You want to build a blog with incremental builds in Astro. You fetch posts from an API and want only new or updated posts to rebuild. Which approach correctly implements this?

hard

A. Use getStaticProps only once to fetch all posts and build all pages at once

B. Use getStaticPaths to list all post IDs, then getStaticProps to fetch data for each ID

C. Use client-side fetching only, no static generation

D. Manually rebuild the entire site on every post update

Solution

1. Step 1: Understand incremental build with data fetching

   Incremental builds require listing pages (post IDs) with getStaticPaths and fetching data per page with getStaticProps.

2. Step 2: Match approach to requirement

   Use getStaticPaths to list all post IDs, then getStaticProps to fetch data for each ID uses getStaticPaths to specify posts and getStaticProps to fetch each post's data, enabling incremental rebuilds.

3. Final Answer:

   Use getStaticPaths to list all post IDs, then getStaticProps to fetch data for each ID -> Option B

4. Quick Check:

   Incremental builds = getStaticPaths + getStaticProps [OK]

Hint: List pages then fetch data per page for incremental builds [OK]

Common Mistakes:

• Fetching all posts at once disables incremental builds
• Relying only on client-side fetching loses static benefits
• Rebuilding entire site wastes time and defeats incremental purpose