@use directive for imports in SASS - Performance & Optimization

Performance: @use directive for imports

MEDIUM IMPACT

This affects CSS build time and runtime style calculation by managing how stylesheets are imported and scoped.

Importing shared styles or variables in multiple Sass files

SASS

@use 'variables' as vars;

.button {
  color: vars.$primary-color;
}

The @use directive imports the file once and scopes variables, preventing duplication.

📈 Performance GainReduces CSS size and speeds up style calculation, improving LCP

Importing shared styles or variables in multiple Sass files

SASS

@import 'variables';
@import 'variables';

.button {
  color: $primary-color;
}

Repeated @import causes the same file to be included multiple times, increasing CSS size and build time.

📉 Performance CostAdds redundant CSS rules, increasing CSS file size and blocking rendering longer

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
@import repeated	N/A	N/A	High due to large CSS	[X] Bad
@use once with namespace	N/A	N/A	Lower due to smaller CSS	[OK] Good

Rendering Pipeline

The @use directive affects the CSS compilation step before the browser renders. It controls how stylesheets are combined and scoped, impacting style calculation and layout.

→Style Calculation

→Layout

→Paint

⚠️ BottleneckStyle Calculation due to redundant or large CSS

Core Web Vital Affected

LCP

This affects CSS build time and runtime style calculation by managing how stylesheets are imported and scoped.

Optimization Tips

1Use @use to import Sass files once and scope variables.

2Avoid multiple @import of the same file to prevent CSS duplication.

3Smaller CSS files improve style calculation and LCP.

Performance Quiz - 3 Questions

What is a key performance benefit of using @use instead of @import in Sass?

A It automatically minifies CSS files

B It imports styles only once and scopes variables to avoid duplication

C It delays CSS loading until after page load

D It converts Sass to CSS faster at runtime

DevTools: Network

How to check: Open DevTools > Network tab > filter by CSS files > check CSS file sizes and number of requests

What to look for: Look for smaller CSS file size and fewer duplicate styles indicating efficient imports

Practice

1. What is the main purpose of the @use directive in Sass?

easy

A. To import Sass files with a namespace to avoid conflicts

B. To directly copy CSS styles without any namespace

C. To run JavaScript code inside Sass files

D. To export variables from Sass files

Solution

1. Step 1: Understand the role of @use

   The @use directive imports Sass files and applies a namespace to their contents.

2. Step 2: Compare with other import methods

   Unlike @import, @use avoids naming conflicts by requiring namespace prefixes.

3. Final Answer:

   To import Sass files with a namespace to avoid conflicts -> Option A

4. Quick Check:

   @use adds namespace = C [OK]

Hint: Remember: @use always adds a namespace [OK]

Common Mistakes:

• Thinking @use copies styles without namespace
• Confusing @use with JavaScript execution
• Believing @use exports variables

2. Which of the following is the correct syntax to import a Sass file named colors.scss using @use?

easy

A. @use 'colors';

B. @use colors.scss;

C. @use "colors.scss";

D. @use colors;

Solution

1. Step 1: Check correct quoting and file extension

   The @use directive requires the file path as a string without the extension, usually quoted.

2. Step 2: Validate options

   @use 'colors'; uses quotes and omits the extension, which is correct. Options B and C include the extension incorrectly or wrong quotes. @use colors; lacks quotes.

3. Final Answer:

   @use 'colors'; -> Option A

4. Quick Check:

   Quotes + no extension = D [OK]

Hint: Use quotes and omit .scss extension in @use [OK]

Common Mistakes:

• Including the .scss extension inside @use
• Not using quotes around the file name
• Using double quotes inconsistently

3. Given the following Sass files, what will be the color of the h1 text?

@use 'colors';
h1 {
  color: colors.$primary;
}

// colors.scss
$primary: blue;
$secondary: green;

medium

A. green

B. black

C. red

D. blue

Solution

1. Step 1: Identify the imported variables

   The @use 'colors'; imports variables with the namespace colors. The variable $primary is set to blue.

2. Step 2: Check the usage in h1

   The color is set to colors.$primary, which refers to blue.

3. Final Answer:

   blue -> Option D

4. Quick Check:

   Namespace + variable = blue [OK]

Hint: Namespace.variable accesses imported values [OK]

Common Mistakes:

• Forgetting to use the namespace prefix
• Confusing $primary with $secondary
• Assuming default color without import

4. What is wrong with this Sass code?

@use 'theme';
h1 {
  color: $main-color;
}

// theme.scss
$main-color: red;

medium

A. The file path must include the .scss extension

B. Using as * is invalid syntax in @use

C. Variables must be accessed with namespace prefix unless configured

D. Variables cannot be used inside selectors

Solution

1. Step 1: Understand @use namespace behavior

   By default, variables must be accessed with the namespace prefix unless as * is used to remove it.

2. Step 2: Check the code usage

   The code uses @use 'theme'; without as *, so variables must be accessed with the theme. prefix, but $main-color is used without it, causing an undefined variable error.

3. Step 3: Identify the actual problem

   Without as *, the prefix is required, so Variables must be accessed with namespace prefix unless configured identifies the issue.

4. Final Answer:

   Variables must be accessed with namespace prefix unless configured -> Option C

5. Quick Check:

   Default namespace prefix required = A [OK]

Hint: Use namespace or as * to access variables directly [OK]

Common Mistakes:

• Thinking as * is invalid syntax
• Forgetting to prefix variables without as *
• Including .scss extension in @use

5. You want to import variables.scss but rename its namespace to vars and override the variable $font-size to 1.5rem. Which @use syntax is correct?

hard

A. @use 'variables' as vars ($font-size: 1.5rem);

B. @use 'variables' as vars with ($font-size: 1.5rem);

C. @use 'variables' with ($font-size: 1.5rem) as vars;

D. @use 'variables' rename vars with ($font-size: 1.5rem);

Solution

1. Step 1: Recall @use syntax for renaming and configuring

   The correct syntax is @use 'file' as namespace with (variable overrides);.

2. Step 2: Match options to syntax

   @use 'variables' as vars with ($font-size: 1.5rem); matches the correct order and syntax. Options B, C, and D have incorrect order or keywords.

3. Final Answer:

   @use 'variables' as vars with ($font-size: 1.5rem); -> Option B

4. Quick Check:

   Namespace + with (overrides) = A [OK]

Hint: Use as then with for renaming and overrides [OK]

Common Mistakes:

• Swapping as and with order
• Using invalid keywords like rename
• Omitting parentheses around overrides