Why Astro handles styles efficiently - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import a CSS file in an Astro component.

Astro

---
import '[1]';
---

<div>Hello Astro!</div>

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

A./styles.css

Bapp.jsx

Cindex.html

Dstyles.js

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to import JavaScript or HTML files as styles.

Forgetting to include the file extension.

Astro imports CSS files directly using the import statement with the CSS file path.

2fill in blank

medium

Complete the code to add scoped styles inside an Astro component.

Astro

<style [1]>
  p { color: blue; }
</style>

<p>This text is blue and scoped.</p>

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

Alocal

Bglobal

Cmodule

Dscoped

Attempts:

3 left

💡 Hint

Common Mistakes

Using global which applies styles globally.

Using unsupported attributes like module or local.

Using scoped attribute in Astro's <style> tag scopes styles to the component only.

3fill in blank

hard

Identify the CSS import that causes unused CSS to load unnecessarily.

Astro

---
import '[1]';
---

<div>Content without styles</div>

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

A./styles.css

B./reset.css

C./unused.css

D./theme.css

Attempts:

3 left

💡 Hint

Common Mistakes

Importing all CSS files regardless of usage.

Not removing unused CSS imports.

Astro includes all imported CSS by default, even if unused. Importing ./unused.css causes unnecessary loading since the component has no matching elements.

4fill in blank

hard

Fill both blanks to create a style block that applies globally and one scoped style.

Astro

<style [1]>
  body { margin: 0; }
</style>

<style [2]>
  h1 { color: red; }
</style>

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

Aglobal

Bscoped

Cmodule

Dlocal

Attempts:

3 left

💡 Hint

Common Mistakes

Using scoped styles for global rules.

Using global styles for component-specific rules.

The first style block uses global to apply styles to the whole page. The second uses scoped to limit styles to the component.

5fill in blank

hard

Fill all three blanks to create a style object with dynamic class names and conditional styles in Astro.

Astro

---
const isActive = true;
const styles = {
  button: '[1]',
  active: isActive ? '[2]' : '',
  disabled: '[3]'
};
---

<button class="{styles.button} {styles.active} {styles.disabled}">Click me</button>

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

Abtn

Bbtn-active

Cbtn-disabled

Dbtn-primary

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect class names that don't match CSS.

Not using conditional logic for active state.

Class names are assigned dynamically. button uses btn, active uses btn-active if active, and disabled uses btn-disabled.

Practice

1. Why does Astro load styles only for components used on a page?

easy

A. To force all styles to be inline in the HTML

B. To make the styles global across all pages automatically

C. To increase the size of the CSS bundle for caching

D. To keep the website fast and avoid loading unnecessary styles

Solution

1. Step 1: Understand Astro's style loading behavior

   Astro only loads styles for components actually used on the page, not all styles globally.

2. Step 2: Reason about the effect of loading only used styles

   This reduces the amount of CSS sent to the browser, making the page load faster and avoiding unused styles.

3. Final Answer:

   To keep the website fast and avoid loading unnecessary styles -> Option D

4. Quick Check:

   Loading only used styles = faster pages [OK]

Hint: Astro loads styles only for used components to speed up pages [OK]

Common Mistakes:

• Thinking Astro loads all styles globally
• Assuming styles are always inline
• Believing style size increases for caching

2. Which of the following is the correct way to add scoped styles in an Astro component?

easy

A.

B.

C.

D.

Solution

1. Step 1: Identify how Astro supports scoped styles

   Astro uses plain <style> tags for scoped styles applied only to the component.

2. Step 2: Compare options for style scoping

   Plain <style> applies scoped styles correctly. <style global> is for global styles. Attributes like inline or scoped are invalid.

3. Final Answer:

   <style> h1 { color: red; } </style> -> Option B

4. Quick Check:

   Scoped styles use <style> [OK]

Hint: Use <style> for component-specific styles in Astro [OK]

Common Mistakes:

• Using
• Using invalid attributes like inline or scoped
• Confusing global and scoped style behaviors

3. Given this Astro component code:

<script>
  export let active = false;
</script>

<style>
  .highlight { color: green; }
</style>

<div class={active ? 'highlight' : ''}>Hello</div>

What happens to the styles if this component is NOT used on a page?

medium

A. The .highlight style is not loaded on that page

B. The .highlight style is loaded globally anyway

C. The page will throw a style loading error

D. The style is converted to inline styles automatically

Solution

1. Step 1: Understand Astro's style loading for unused components

   Astro only includes styles for components actually used on the page, so unused component styles are skipped.

2. Step 2: Apply this to the given component

   If the component with the .highlight style is not used, its styles are not included in the page's CSS.

3. Final Answer:

   The .highlight style is not loaded on that page -> Option A

4. Quick Check:

   Unused component styles = not loaded [OK]

Hint: Unused component styles are skipped to keep CSS small [OK]

Common Mistakes:

• Assuming all component styles load globally
• Thinking unused styles cause errors
• Believing styles become inline automatically

4. You wrote this Astro component style:

<style>
  .btn { background: blue; }
</style>

But the button does not get the blue background on the page. What is the most likely cause?

medium

A. Astro requires styles to be global to work

B. Scoped styles do not apply to class selectors

C. The component is not used on the page, so styles are not loaded

D. The CSS syntax is invalid and ignored

Solution

1. Step 1: Check if the component is included on the page

   If the component is not used, Astro will not load its scoped styles, so the button won't get styled.

2. Step 2: Verify style syntax and scoping

   The CSS syntax is valid and scoped styles apply to class selectors, so these are not the issue.

3. Final Answer:

   The component is not used on the page, so styles are not loaded -> Option C

4. Quick Check:

   Unused component = no styles loaded [OK]

Hint: Check if component is on page; unused means no styles loaded [OK]

Common Mistakes:

• Thinking scoped styles don't work with classes
• Believing Astro needs global styles only
• Assuming CSS syntax error without checking

5. You want to create a page with multiple Astro components, each with their own scoped styles, but also share a global font style. How should you organize your styles for best performance and clarity?

hard

A. Use <style global> for the font in a layout component and <style> in each component for specific styles

B. Put all styles in one global <style> tag in every component

C. Use only <style scoped> everywhere, including global fonts

D. Inline all styles directly on HTML elements to avoid loading issues

Solution

1. Step 1: Separate global and component styles

   Global styles like fonts should be placed in a <style global> block, often in a layout component used by all pages.

2. Step 2: Use scoped styles for component-specific CSS

   Each component should have its own <style> for scoped styles to avoid conflicts and keep styles modular.

3. Step 3: Combine for performance and clarity

   This approach loads global styles once and component styles only when components are used, improving performance and maintainability.

4. Final Answer:

   Use <style global> for the font in a layout component and <style> in each component for specific styles -> Option A

5. Quick Check:

   Global + scoped styles combined = best practice [OK]

Hint: Global styles in layout, scoped styles in components for best results [OK]

Common Mistakes:

• Putting all styles global causing conflicts
• Using <style> for global fonts without global modifier
• Inlining styles everywhere causing clutter