Dev server and build process in Astro - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the dev server in Astro?

The dev server in Astro runs your project locally, showing live updates as you change files. It helps you see your site instantly without rebuilding manually.

beginner

What does the build process do in Astro?

The build process prepares your site for production by optimizing files, bundling assets, and creating static HTML pages ready to be deployed.

intermediate

How does Astro's dev server improve developer experience?

Astro's dev server watches your files and reloads the browser automatically when you save changes, making development fast and smooth.

beginner

What command do you use to start the dev server in Astro?

You run npm run dev or astro dev to start the dev server and preview your site locally.

intermediate

Why is the build output in Astro usually smaller and faster?

Because Astro only sends the needed HTML, CSS, and JavaScript to the browser, removing unused code and optimizing assets during build.

What does the Astro dev server do?

A Converts JavaScript to Python

B Deploys your site to the internet

C Deletes unused files automatically

D Runs your site locally with live updates

The dev server runs your site locally and updates it live as you make changes.

Which command starts the Astro build process?

A astro dev

B npm run build

C astro start

D npm run serve

The build process is started with npm run build to prepare the site for production.

What is a key benefit of Astro's build process?

A It optimizes and reduces site size for faster loading

B It disables JavaScript on the site

C It bundles all code into one big file

D It automatically writes content for you

Astro optimizes and reduces the site size during build for better performance.

How does Astro's dev server help during development?

A By automatically reloading the browser on file changes

B By sending emails when you save files

C By compiling code to machine language

D By blocking internet access

The dev server watches files and reloads the browser automatically to show changes.

What kind of output does Astro produce after build?

A Raw source code files

B Only JavaScript files

C Static HTML, CSS, and optimized JavaScript files

D Database entries

Astro produces static HTML, CSS, and optimized JavaScript ready for deployment.

Explain how the Astro dev server works and why it is useful during development.

Think about how you see your changes immediately when coding.

Describe the steps and benefits of the Astro build process for preparing a website for production.

Consider what happens before you upload your site to the internet.

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