Component variant generation in SASS - Performance & Optimization

Performance: Component variant generation

MEDIUM IMPACT

This affects CSS bundle size and rendering speed by controlling how many CSS rules are generated and applied.

Creating multiple style variants for a button component

SASS

$button-colors: (primary: blue, secondary: gray, danger: red, success: green, warning: orange, info: teal);
@each $name, $color in $button-colors {
  .btn-#{$name} {
    background-color: $color;
    padding: 1rem;
    border-radius: 0.5rem;
  }
}

Uses a map and loop to generate variants efficiently, reducing repetition and CSS size.

📈 Performance GainSaves ~1-2kb by avoiding redundant code and reduces style recalculations

Creating multiple style variants for a button component

SASS

@mixin button-variant($name, $color) { .btn-#{$name} { background-color: $color; padding: 1rem; border-radius: 0.5rem; } }
@include button-variant('primary', blue);
@include button-variant('secondary', gray);
@include button-variant('danger', red);
@include button-variant('success', green);
@include button-variant('warning', orange);
@include button-variant('info', teal);

Generates separate CSS rules for each variant, increasing CSS size and causing longer style calculation.

📉 Performance CostAdds ~3-5kb to CSS bundle and triggers multiple style recalculations on load

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Many explicit variant classes	Low	Low	Medium (due to large CSS)	[X] Bad
Variant generation with loops and maps	Low	Low	Low	[OK] Good

Rendering Pipeline

Sass compiles variant styles into CSS rules. More variants mean more CSS selectors and declarations, increasing style calculation and paint time.

→Style Calculation

→Layout

→Paint

⚠️ BottleneckStyle Calculation due to many CSS selectors

Core Web Vital Affected

LCP

This affects CSS bundle size and rendering speed by controlling how many CSS rules are generated and applied.

Optimization Tips

1Avoid generating unused or excessive CSS variants.

2Use Sass loops and maps to create variants efficiently.

3Keep CSS bundle size small to improve page load and rendering speed.

Performance Quiz - 3 Questions

What is a main performance risk of generating many CSS component variants?

A More JavaScript execution time

B Increased CSS bundle size and slower style calculation

C Higher DOM node count

D Slower image loading

DevTools: Performance

How to check: Record page load and observe Style Recalculation and Layout timings; check CSS size in Network panel.

What to look for: Long Style Recalculation or large CSS file size indicates inefficient variant generation.

Practice

1. What is the main purpose of component variant generation in Sass?

easy

A. To create multiple style versions of the same component easily

B. To write JavaScript inside Sass files

C. To compile Sass into JavaScript

D. To remove unused CSS automatically

Solution

1. Step 1: Understand component variants

   Component variants allow creating different styles for the same element, like buttons with different colors.

2. Step 2: Identify the main purpose

   The main goal is to generate these style versions easily and keep code organized.

3. Final Answer:

   To create multiple style versions of the same component easily -> Option A

4. Quick Check:

   Component variant generation = multiple style versions [OK]

Hint: Variants mean different styles for one component [OK]

Common Mistakes:

• Confusing Sass with JavaScript
• Thinking Sass compiles to JS
• Believing variants remove unused CSS

2. Which Sass syntax correctly defines a mixin for generating button variants with a dynamic color?

easy

A. @include button-variant($color) { background-color: $color; }

B. @function button-variant($color) { background-color: $color; }

C. @extend button-variant($color) { background-color: $color; }

D. @mixin button-variant($color) { background-color: $color; }

Solution

1. Step 1: Identify mixin syntax

   Mixins use '@mixin' to define reusable style blocks with parameters.

2. Step 2: Check options

   @mixin button-variant($color) { background-color: $color; } uses '@mixin' correctly; others misuse '@function', '@include', or '@extend'.

3. Final Answer:

   @mixin button-variant($color) { background-color: $color; } -> Option D

4. Quick Check:

   Mixin definition starts with '@mixin' [OK]

Hint: Define mixins with '@mixin', not '@function' or '@include' [OK]

Common Mistakes:

• Using '@function' instead of '@mixin'
• Trying to define styles inside '@include'
• Confusing '@extend' with mixin definition

3. Given the Sass code:

@mixin variant($name, $color) {
  .btn-#{$name} {
    background-color: $color;
  }
}

@include variant('primary', blue);
@include variant('danger', red);

What CSS will this generate?

medium

A. .btn-primary { background-color: blue; }
.btn-danger { background-color: red; }

B. .btn-#primary { background-color: blue; }
.btn-#danger { background-color: red; }

C. .btn-primary { color: blue; }
.btn-danger { color: red; }

D. .btn-primary { background-color: $color; }
.btn-danger { background-color: $color; }

Solution

1. Step 1: Understand interpolation in class names

   The '#{$name}' inside '.btn-#{$name}' inserts the string value of $name, creating '.btn-primary' and '.btn-danger'.

2. Step 2: Check property values

   The background-color uses the passed $color values 'blue' and 'red' correctly.

3. Final Answer:

   .btn-primary { background-color: blue; } .btn-danger { background-color: red; } -> Option A

4. Quick Check:

   Interpolation creates correct class names [OK]

Hint: Use #{} to insert variables in selectors [OK]

Common Mistakes:

• Leaving interpolation as literal text
• Confusing background-color with color property
• Not passing parameters correctly

4. What is wrong with this Sass code for generating variants?

@mixin variant($name, $color) {
  .btn-$name {
    background-color: $color;
  }
}

@include variant('success', green);

medium

A. Cannot use variables in mixin parameters

B. Incorrect property name 'background-color'

C. Missing interpolation for $name in the selector

D. Mixin cannot be included with parameters

Solution

1. Step 1: Check selector syntax

   Variables inside selectors need interpolation with '#{}'. Here '.btn-$name' misses '#{}'.

2. Step 2: Understand interpolation usage

   Correct syntax is '.btn-#{$name}' to insert the variable value.

3. Final Answer:

   Missing interpolation for $name in the selector -> Option C

4. Quick Check:

   Use '#{}' to insert variables in selectors [OK]

Hint: Use #{} around variables in selectors [OK]

Common Mistakes:

• Forgetting interpolation syntax
• Thinking variables can't be in selectors
• Misusing mixin parameters

5. You want to generate button variants for 'primary', 'secondary', and 'danger' with colors blue, gray, and red using a Sass map and a mixin. Which code correctly creates all variants with minimal repetition?

hard

A. @mixin variants($map) {
.btn {
background-color: map-get($map, primary);
}
}
$btn-colors: (primary: blue, secondary: gray, danger: red);
@include variants($btn-colors);

B. @mixin variants($map) {
@each $name, $color in $map {
.btn-#{$name} {
background-color: $color;
}
}
}
$btn-colors: (primary: blue, secondary: gray, danger: red);
@include variants($btn-colors);

C. @mixin variants($map) {
@for $i from 1 through length($map) {
.btn-#{$i} {
background-color: nth($map, $i);
}
}
}
$btn-colors: (blue, gray, red);
@include variants($btn-colors);

D. @mixin variants($map) {
@each $color in $map {
.btn-#{$color} {
background-color: $color;
}
}
}
$btn-colors: (blue, gray, red);
@include variants($btn-colors);

Solution

1. Step 1: Understand map usage with @each

   Using '@each $name, $color in $map' loops over keys and values, perfect for named variants.

2. Step 2: Check each option's approach

   @mixin variants($map) { @each $name, $color in $map { .btn-#{$name} { background-color: $color; } } } $btn-colors: (primary: blue, secondary: gray, danger: red); @include variants($btn-colors); correctly loops over a map with names and colors, generating '.btn-primary', '.btn-secondary', '.btn-danger' with correct colors.

3. Step 3: Identify issues in other options

   @mixin variants($map) { .btn { background-color: map-get($map, primary); } } $btn-colors: (primary: blue, secondary: gray, danger: red); @include variants($btn-colors); only styles '.btn' once, ignoring variants. @mixin variants($map) { @for $i from 1 through length($map) { .btn-#{$i} { background-color: nth($map, $i); } } } $btn-colors: (blue, gray, red); @include variants($btn-colors); uses numeric indexes without names. @mixin variants($map) { @each $color in $map { .btn-#{$color} { background-color: $color; } } } $btn-colors: (blue, gray, red); @include variants($btn-colors); loops colors but uses color names as class names incorrectly.

4. Final Answer:

   @mixin variants($map) { @each $name, $color in $map { .btn-#{$name} { background-color: $color; } } } $btn-colors: (primary: blue, secondary: gray, danger: red); @include variants($btn-colors); -> Option B

5. Quick Check:

   Use @each with map keys and values for variants [OK]

Hint: Use @each with map keys and values for variant generation [OK]

Common Mistakes:

• Looping only colors without names
• Using numeric loops without keys
• Not generating separate classes per variant