CSS Modules support in Astro - Performance & Optimization

Performance: CSS Modules support

MEDIUM IMPACT

This affects page load speed by controlling CSS scope and bundle size, impacting render blocking and style recalculation.

Applying styles scoped to components without global conflicts

Astro

import styles from './Button.module.css';

<div className={styles.primary}>Click me</div>

CSS Modules load only styles used by the component, reducing CSS size and avoiding global style recalculations.

📈 Performance GainSaves 30-70kb CSS, reduces render-blocking CSS, limits style recalculation to scoped elements

Applying styles scoped to components without global conflicts

Astro

/* global.css loaded everywhere */
import './global.css';

<div class="button primary">Click me</div>

Global CSS loads all styles on every page, increasing bundle size and causing unnecessary style recalculations.

📉 Performance CostAdds 50-100kb to CSS bundle, blocks rendering until CSS loads, triggers style recalculation for all elements

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Global CSS	N/A	Multiple reflows on style changes	High paint cost due to large CSS	[X] Bad
CSS Modules	Scoped to component nodes	Single reflow limited to component	Lower paint cost with smaller CSS	[OK] Good

Rendering Pipeline

CSS Modules generate scoped CSS classes that the browser applies only to relevant elements, reducing style recalculation and repaint.

→Style Calculation

→Layout

→Paint

⚠️ BottleneckStyle Calculation due to large global CSS

Core Web Vital Affected

LCP

This affects page load speed by controlling CSS scope and bundle size, impacting render blocking and style recalculation.

Optimization Tips

1Scope CSS to components to reduce unused styles and bundle size.

2Avoid large global CSS files that block rendering and cause style recalculations.

3Use CSS Modules to limit style recalculation and improve Largest Contentful Paint.

Performance Quiz - 3 Questions

How does CSS Modules support improve page load performance compared to global CSS?

A By loading all CSS globally to avoid multiple requests

B By scoping CSS to components, reducing unused styles and render-blocking CSS

C By increasing CSS bundle size for better caching

D By disabling CSS animations to reduce paint cost

DevTools: Performance

How to check: Record a page load and interaction; look for style recalculation and layout shifts in the flame chart.

What to look for: Lower style recalculation time and fewer layout shifts indicate better CSS scoping and performance.

Practice

1. What is the main benefit of using CSS Modules in Astro components?

easy

A. They keep styles local to components, avoiding conflicts.

B. They automatically minify CSS for faster loading.

C. They allow inline styles directly in HTML tags.

D. They enable global styles to override component styles.

Solution

1. Step 1: Understand CSS Modules purpose

   CSS Modules scope styles locally to components to prevent style conflicts.

2. Step 2: Compare options

   Only They keep styles local to components, avoiding conflicts. correctly describes this main benefit; others describe unrelated features.

3. Final Answer:

   They keep styles local to components, avoiding conflicts. -> Option A

4. Quick Check:

   CSS Modules = Local styles [OK]

Hint: Remember CSS Modules isolate styles to components [OK]

Common Mistakes:

• Thinking CSS Modules minify CSS automatically
• Confusing CSS Modules with inline styles
• Assuming CSS Modules create global styles

2. Which is the correct way to import a CSS Module file named styles.module.css in an Astro component?

easy

A. import './styles.module.css';

B. import styles from './styles.css';

C. const styles = require('./styles.module.css');

D. import styles from './styles.module.css';

Solution

1. Step 1: Identify correct import syntax for CSS Modules

   CSS Modules require importing the CSS file as an object, typically with import styles from './filename.module.css';.

2. Step 2: Check file extension and import style

   import styles from './styles.module.css'; uses the correct file extension and import syntax. import './styles.module.css'; imports without assigning, C uses CommonJS which is not standard in Astro, and D imports a non-module CSS file.

3. Final Answer:

   import styles from './styles.module.css'; -> Option D

4. Quick Check:

   Import CSS Modules as objects with .module.css [OK]

Hint: Use import with .module.css and assign to a variable [OK]

Common Mistakes:

• Forgetting to assign import to a variable
• Using require instead of import
• Importing non-module CSS files as modules

3. Given the CSS Module import import styles from './button.module.css'; and the CSS file containing .primary { color: blue; }, what will be the rendered class attribute for <button class={styles.primary}>Click</button>?

medium

A. class="button_primary__abc123"

B. class="primary"

C. class="styles.primary"

D. class="undefined"

Solution

1. Step 1: Understand CSS Modules class naming

   CSS Modules transform class names to unique strings like button_primary__abc123 to avoid conflicts.

2. Step 2: Analyze the rendered class attribute

   Using styles.primary applies the transformed unique class name, not the original 'primary'. So the class attribute will be a unique hashed string.

3. Final Answer:

   class="button_primary__abc123" -> Option A

4. Quick Check:

   CSS Modules generate unique class names [OK]

Hint: CSS Modules rename classes to unique strings [OK]

Common Mistakes:

• Expecting original class name without transformation
• Using the variable name as class string
• Getting undefined if import is wrong

4. What is wrong with this Astro component code using CSS Modules?

import styles from './card.module.css';

export default function Card() {
  return <div class="styles.card">Content</div>;
}

medium

A. The component must be a class, not a function.

B. The class attribute should use curly braces, not quotes.

C. The import statement is missing the .module.css extension.

D. CSS Modules cannot be used in Astro components.

Solution

1. Step 1: Check how class names are applied with CSS Modules

   CSS Modules require using curly braces to insert the imported class object value, e.g., class={styles.card}.

2. Step 2: Identify the error in the code

   The code uses quotes around "styles.card", which treats it as a string literal, not the variable. This causes the class to be literally 'styles.card' instead of the hashed class.

3. Final Answer:

   The class attribute should use curly braces, not quotes. -> Option B

4. Quick Check:

   Use curly braces to apply CSS Module classes [OK]

Hint: Use {styles.className} not "styles.className" for CSS Modules [OK]

Common Mistakes:

• Using quotes instead of curly braces for class binding
• Forgetting .module.css in import
• Thinking Astro requires class components

5. How can you apply multiple CSS Module classes styles.primary and styles.rounded to a single element in an Astro component?

hard

A. <div class={styles.primary, styles.rounded}>Content</div>

B. <div class="styles.primary styles.rounded">Content</div>

C. <div class={`${styles.primary} ${styles.rounded}`}>Content</div>

D. <div class={styles.primary + styles.rounded}>Content</div>

Solution

1. Step 1: Understand combining multiple CSS Module classes

   To apply multiple classes, you join their values as strings separated by spaces, typically using template literals or string concatenation.

2. Step 2: Analyze each option

   <div class={`${styles.primary} ${styles.rounded}`}>Content</div> correctly uses template literals to combine classes with a space. <div class="styles.primary styles.rounded">Content</div> treats class names as literal strings, not variables. <div class={styles.primary + styles.rounded}>Content</div> concatenates without space, merging class names incorrectly. <div class={styles.primary, styles.rounded}>Content</div> uses comma which is invalid syntax.

3. Final Answer:

   <div class={`${styles.primary} ${styles.rounded}`}>Content</div> -> Option C

4. Quick Check:

   Join CSS Module classes with space in template literals [OK]

Hint: Use template literals with spaces to combine CSS Module classes [OK]

Common Mistakes:

• Using quotes instead of variables for class names
• Concatenating without spaces
• Using commas inside class attribute