Dev server and build process in Astro - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start the Astro development server.

Astro

npm run [1]

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

Abuild

Bdev

Cstart

Dserve

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'build' instead of 'dev' to start the server.

Using 'start' which is not the default dev command.

Running npm run dev starts the Astro development server, allowing live preview and hot reload.

2fill in blank

medium

Complete the code to create a production build in Astro.

Astro

npm run [1]

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

Aserve

Bdev

Cbuild

Dpreview

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'dev' instead of 'build' to create production files.

Using 'serve' which is for previewing builds.

npm run build compiles your Astro project into static files for production.

3fill in blank

hard

Fix the error in the command to preview the production build locally.

Astro

npm run [1]

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

Astart

Bdev

Cbuild

Dpreview

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'start' which may not serve the build correctly.

Using 'dev' which runs the development server.

npm run preview serves the production build locally so you can test it before deployment.

4fill in blank

hard

Fill both blanks to complete the Astro config for build output directory and base path.

Astro

export default {
  build: {
    outDir: '[1]',
    base: '[2]'
  }
}

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

Adist

B/

Cpublic

D/app/

Attempts:

3 left

💡 Hint

Common Mistakes

Setting base to '/app/' when deploying to root.

Using 'public' as output directory which is for static assets.

The outDir is usually set to dist for build files, and base is / for root path.

5fill in blank

hard

Fill all three blanks to complete the npm scripts for dev, build, and preview in package.json.

Astro

"scripts": {
  "dev": "astro [1]",
  "build": "astro [2]",
  "preview": "astro [3]"
}

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

Adev

Bbuild

Cpreview

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'start' instead of 'preview' for preview script.

Mixing up build and dev commands.

These scripts run the Astro commands for development, building, and previewing respectively.

Practice

1. What is the main purpose of the astro dev command in Astro?

easy

A. To start a development server that shows live updates as you code

B. To create optimized production files for deployment

C. To install Astro dependencies automatically

D. To generate static HTML files without a server

Solution

1. Step 1: Understand the role of astro dev

   The astro dev command runs a local server that watches your files and reloads the browser when you make changes.

2. Step 2: Differentiate from build process

   The build process (astro build) creates optimized files for publishing, not live updates.

3. Final Answer:

   To start a development server that shows live updates as you code -> Option A

4. Quick Check:

   Dev server = live updates [OK]

Hint: Dev server shows live changes, build prepares files [OK]

Common Mistakes:

• Confusing dev server with build output
• Thinking astro dev creates production files
• Assuming astro dev installs packages

2. Which of the following is the correct command to build your Astro project for production?

easy

A. astro run

B. astro start

C. astro build

D. astro serve

Solution

1. Step 1: Recall Astro build command

   The command astro build is used to create optimized production files for deployment.

2. Step 2: Verify other commands

   astro start, astro run, and astro serve are not valid build commands in Astro.

3. Final Answer:

   astro build -> Option C

4. Quick Check:

   Build command = astro build [OK]

Hint: Build = astro build, dev = astro dev [OK]

Common Mistakes:

• Using astro start instead of astro build
• Confusing astro serve with build command
• Trying astro run which doesn't exist

3. Given the following commands run in order:

astro dev
astro build
astro dev

What will happen when you run the last astro dev command?

medium

A. It will overwrite the build files with development files

B. It will start the dev server showing live updates again

C. It will throw an error because build was already done

D. It will serve the optimized build files instead of dev server

Solution

1. Step 1: Understand astro dev behavior

   Each time you run astro dev, it starts a fresh development server with live reload, independent of previous builds.

2. Step 2: Recognize build does not block dev

   Running astro build creates production files but does not prevent running astro dev again later.

3. Final Answer:

   It will start the dev server showing live updates again -> Option B

4. Quick Check:

   Dev server always starts fresh on astro dev [OK]

Hint: Dev server can run anytime, build doesn't block it [OK]

Common Mistakes:

• Thinking build locks out dev server
• Assuming dev overwrites build files
• Expecting errors after build when running dev

4. You run astro build but the output folder is empty. What is the most likely cause?

medium

A. You forgot to run astro dev first

B. The build command only works after publishing

C. Your project folder is missing the package.json file

D. There is a syntax error in your Astro files stopping the build

Solution

1. Step 1: Check build requirements

   astro build requires valid Astro files; syntax errors prevent successful build output.

2. Step 2: Eliminate other causes

   astro dev is not required before build; build works locally before publishing; missing package.json usually causes install errors, not empty build.

3. Final Answer:

   There is a syntax error in your Astro files stopping the build -> Option D

4. Quick Check:

   Syntax errors block build output [OK]

Hint: Check syntax errors if build folder is empty [OK]

Common Mistakes:

• Thinking dev must run before build
• Assuming build only works after publishing
• Ignoring syntax errors in source files

5. You want to deploy your Astro site but notice the build output is very large and slow to load. Which combination of steps will best optimize your build process?

hard

A. Run astro build with image optimization enabled and remove unused CSS

B. Only run astro dev and deploy the dev server files

C. Skip astro build and upload source files directly

D. Run astro build without any configuration changes

Solution

1. Step 1: Identify optimization techniques

   Enabling image optimization and removing unused CSS during build reduces file size and improves load speed.

2. Step 2: Understand deployment best practices

   Deploying dev server files or source files directly is inefficient and not recommended; default build may not optimize assets fully.

3. Final Answer:

   Run astro build with image optimization enabled and remove unused CSS -> Option A

4. Quick Check:

   Optimize images + CSS during build = faster site [OK]

Hint: Optimize images and CSS during build for faster sites [OK]

Common Mistakes:

• Deploying dev server files instead of build output
• Skipping build and uploading source files
• Not enabling optimizations in build config