Source maps for debugging in SASS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a source map in the context of Sass debugging?

A source map is a file that links the compiled CSS back to the original Sass files. It helps browsers show the exact Sass line when inspecting styles, making debugging easier.

beginner

How do you enable source maps when compiling Sass?

You enable source maps by adding the --source-map flag when running the Sass compiler, like sass --source-map input.scss output.css.

beginner

Why are source maps helpful during web development?

Source maps let you see and edit the original Sass code in browser developer tools instead of the compiled CSS. This saves time and reduces confusion when fixing styles.

beginner

What happens if you don’t use source maps with Sass?

Without source maps, browser tools only show the compiled CSS lines. This makes it hard to find where styles come from in your Sass files, slowing down debugging.

intermediate

Can source maps affect website performance?

Source maps do not affect how the website looks or runs for users. They are only used by developer tools and can be disabled in production to keep files smaller.

What command enables source maps when compiling Sass?

A sass --source-map input.scss output.css

B sass --no-source-map input.scss output.css

C sass --map-source input.scss output.css

D sass --debug input.scss output.css

The --source-map flag tells Sass to generate source maps linking CSS to Sass.

What does a source map file do?

A Compiles Sass into CSS

B Minifies CSS for faster loading

C Links compiled CSS back to original Sass files

D Removes unused CSS styles

Source maps connect the CSS you see in the browser to the original Sass code for easier debugging.

If you don’t use source maps, what will browser developer tools show?

A Both Sass and CSS files

B Only the compiled CSS lines

C The original Sass files

D No styles at all

Without source maps, browsers only show the compiled CSS, making it harder to find the original Sass source.

Are source maps visible to website visitors?

A No, they are only used by developer tools

B Yes, they change the website appearance

C Yes, they slow down the website

D No, they delete CSS files

Source maps are for developers only and do not affect the website’s look or speed for visitors.

When should you disable source maps?

A Only when using JavaScript

B During development for easier debugging

C Never, they are always required

D In production to reduce file size

Disabling source maps in production keeps files smaller and avoids exposing source code.

Explain what source maps are and why they are useful when working with Sass.

Think about how you find the original Sass code when inspecting styles.

Describe the steps to enable source maps when compiling Sass and how to check if they work.

Consider the command line and browser inspection.

Practice

1. What is the main purpose of source maps when working with Sass?

easy

A. To convert Sass files into JavaScript

B. To minify the CSS output for faster loading

C. To link compiled CSS back to the original Sass files for easier debugging

D. To automatically fix syntax errors in Sass code

Solution

1. Step 1: Understand what source maps do

   Source maps create a connection between the compiled CSS and the original Sass files.

2. Step 2: Identify the debugging benefit

   This connection helps developers see the original Sass code in browser DevTools, making debugging easier.

3. Final Answer:

   To link compiled CSS back to the original Sass files for easier debugging -> Option C

4. Quick Check:

   Source maps = link CSS to Sass for debugging [OK]

Hint: Source maps help find Sass code from CSS in browser tools [OK]

Common Mistakes:

• Thinking source maps minify CSS
• Believing source maps fix code errors automatically
• Confusing source maps with JavaScript conversion

2. Which command correctly generates a source map when compiling Sass from the command line?

easy

A. sass input.scss output.css --no-source-map

B. sass input.scss output.css --minify

C. sass input.scss output.css --watch

D. sass input.scss output.css --source-map

Solution

1. Step 1: Identify the flag for source maps

   The --source-map flag tells Sass to generate source maps during compilation.

2. Step 2: Check the command options

   sass input.scss output.css --source-map uses --source-map, which is correct. Other options either disable source maps or do unrelated tasks.

3. Final Answer:

   sass input.scss output.css --source-map -> Option D

4. Quick Check:

   Use --source-map flag to generate source maps [OK]

Hint: Look for --source-map flag to enable source maps [OK]

Common Mistakes:

• Using --no-source-map disables source maps
• Confusing --watch with source map generation
• Using --minify does not create source maps

3. Given the Sass file style.scss compiled with source maps, what will you see in browser DevTools when inspecting an element styled by Sass?

medium

A. The original Sass file and line number where the style is defined

B. Only the compiled CSS file with no reference to Sass

C. An error message about missing source maps

D. The JavaScript file controlling styles

Solution

1. Step 1: Understand source map effect in DevTools

   Source maps allow DevTools to show the original Sass file and exact line for styles.

2. Step 2: Identify what is displayed when source maps exist

   With source maps, DevTools shows Sass source, not just compiled CSS, helping debugging.

3. Final Answer:

   The original Sass file and line number where the style is defined -> Option A

4. Quick Check:

   DevTools shows Sass source with source maps [OK]

Hint: Source maps show Sass file and line in DevTools [OK]

Common Mistakes:

• Expecting only CSS without Sass info
• Thinking source maps cause errors in DevTools
• Confusing styles with JavaScript files

4. You compiled Sass with sass input.scss output.css but cannot see Sass source in browser DevTools. What is the likely problem?

medium

A. Your Sass file has syntax errors

B. You forgot to add the --source-map flag during compilation

C. Browser DevTools do not support source maps

D. You need to refresh the Sass compiler

Solution

1. Step 1: Check compilation command for source map flag

   The command lacks --source-map, so no source maps were generated.

2. Step 2: Understand impact on DevTools

   Without source maps, DevTools cannot link CSS back to Sass source files.

3. Final Answer:

   You forgot to add the --source-map flag during compilation -> Option B

4. Quick Check:

   Missing --source-map means no source maps [OK]

Hint: Always add --source-map to see Sass in DevTools [OK]

Common Mistakes:

• Assuming syntax errors cause missing source maps
• Believing DevTools lack source map support
• Thinking refreshing compiler fixes missing source maps

5. You want to debug a complex Sass project with multiple partials and nested imports. How should you configure source maps to best help debugging?

hard

A. Compile Sass with --source-map enabled and use browser DevTools to trace styles back to original partial files

B. Disable source maps to speed up compilation and debug only compiled CSS

C. Manually copy Sass code into CSS comments for debugging

D. Use JavaScript to log Sass variables during runtime

Solution

1. Step 1: Enable source maps during compilation

   Using --source-map generates maps linking CSS to all Sass partials and nested files.

2. Step 2: Use browser DevTools for tracing

   DevTools can then show exact Sass partial and line for each style, simplifying debugging.

3. Final Answer:

   Compile Sass with --source-map enabled and use browser DevTools to trace styles back to original partial files -> Option A

4. Quick Check:

   Enable source maps + DevTools = best debugging [OK]

Hint: Enable source maps and use DevTools for multi-file Sass debugging [OK]

Common Mistakes:

• Disabling source maps thinking it speeds debugging
• Trying to debug by copying Sass into CSS comments
• Using JavaScript logging for Sass variables