Why @use directive for imports in SASS? - Purpose & Use Cases

The Big Idea

Discover how a simple directive can save you hours of messy style fixes!

The Scenario

Imagine you have many style files for your website, and you want to include colors, fonts, and buttons styles in your main style file by copying and pasting all the code manually.

The Problem

Copying and pasting styles everywhere makes your files huge and messy. If you change a color in one place, you have to find and update it everywhere manually, which is slow and causes mistakes.

The Solution

The @use directive lets you bring in styles from other files cleanly and safely. It keeps your code organized and lets you update styles in one place, automatically affecting all files that use them.

Before vs After

✗ Before

@import 'colors';
@import 'fonts';
@import 'buttons';

✓ After

@use 'colors';
@use 'fonts';
@use 'buttons';

What It Enables

You can build neat, reusable style parts that work together without conflicts, making your website easier to maintain and grow.

Real Life Example

When building a company website, you can keep your brand colors in one file and use @use to apply them everywhere. Change the brand color once, and the whole site updates automatically.

Key Takeaways

@use helps organize styles by importing files cleanly.

It avoids repeating code and reduces errors from manual copying.

Updating shared styles becomes simple and automatic.

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