Setting up SASS (npm, dart-sass) - Performance Optimization Steps

Performance: Setting up SASS (npm, dart-sass)

MEDIUM IMPACT

This affects the build time and initial page load speed by how CSS is generated and delivered.

Compiling SASS styles for a website

SASS

Installing dart-sass via npm and running 'sass src/styles:dist/styles --no-source-map' for fast compilation.

Dart-sass is faster, maintained, and integrates well with modern build tools, speeding up CSS generation.

📈 Performance GainReduces build time by 50%+, enables faster CSS delivery, improves LCP.

Compiling SASS styles for a website

SASS

Using an outdated Ruby SASS compiler installed globally and compiling styles manually with slow commands.

Ruby SASS is deprecated and slower, causing longer build times and blocking CSS delivery.

📉 Performance CostBlocks rendering during build, adds seconds to compile time, delays LCP.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Ruby SASS manual compile	N/A	N/A	Blocks CSS delivery delaying paint	[X] Bad
Dart-sass via npm automated compile	N/A	N/A	CSS ready faster, reduces render-blocking	[OK] Good

Rendering Pipeline

SASS compilation happens before the browser rendering pipeline. Faster compilation means CSS is ready sooner, reducing render-blocking time.

→Build Time

→CSS Delivery

→Style Calculation

⚠️ BottleneckBuild Time delays CSS availability, which blocks Style Calculation and delays first paint.

Core Web Vital Affected

LCP

This affects the build time and initial page load speed by how CSS is generated and delivered.

Optimization Tips

1Use dart-sass via npm for faster, modern SASS compilation.

2Automate SASS compilation in your build process to avoid manual delays.

3Check CSS load times in DevTools Network panel to ensure fast delivery.

Performance Quiz - 3 Questions

Why is using dart-sass via npm better for performance than older Ruby SASS?

A Because Ruby SASS produces smaller CSS files.

B Because npm automatically minifies CSS without extra tools.

C Because dart-sass compiles CSS faster, reducing build and load time.

D Because Ruby SASS runs in the browser.

DevTools: Network

How to check: Open DevTools > Network tab, filter by CSS files, reload page and check CSS file load time and blocking time.

What to look for: Look for CSS files loading quickly without blocking main content rendering to confirm fast CSS delivery.

Practice

1. What is the main purpose of using npm when setting up SASS with Dart SASS?

easy

A. To write SASS code directly in the terminal

B. To run a web server for SASS files

C. To convert CSS files into SASS files

D. To install the Dart SASS compiler package

Solution

1. Step 1: Understand npm's role in SASS setup

   npm is a package manager used to install tools like Dart SASS compiler.

2. Step 2: Identify what npm installs for SASS

   npm installs the Dart SASS compiler so you can compile SASS files to CSS.

3. Final Answer:

   To install the Dart SASS compiler package -> Option D

4. Quick Check:

   npm installs packages = B [OK]

Hint: npm installs tools like Dart SASS compiler [OK]

Common Mistakes:

• Thinking npm runs SASS code directly
• Confusing CSS to SASS conversion
• Assuming npm runs a web server

2. Which command correctly installs Dart SASS using npm?

easy

A. npm install -g sass

B. npm sass install

C. npm get sass

D. npm run sass

Solution

1. Step 1: Recall npm install syntax

   The correct npm command to install a package globally is npm install -g <package-name>.

2. Step 2: Match the command to Dart SASS

   For Dart SASS, the package name is sass, so the command is npm install -g sass.

3. Final Answer:

   npm install -g sass -> Option A

4. Quick Check:

   npm install -g package = A [OK]

Hint: Use 'npm install -g package' to install globally [OK]

Common Mistakes:

• Using 'npm sass install' which is invalid syntax
• Confusing 'npm get' with install
• Trying to run sass with 'npm run' without setup

3. What will happen if you run the command sass --watch styles.scss:styles.css in your terminal?

medium

A. It compiles styles.scss to styles.css once and exits

B. It watches styles.scss and updates styles.css on changes

C. It watches styles.css and updates styles.scss on changes

D. It throws an error because of wrong syntax

Solution

1. Step 1: Understand the --watch flag

   The --watch flag tells SASS to monitor the source file for changes continuously.

2. Step 2: Analyze the command's file mapping

   styles.scss:styles.css means compile styles.scss into styles.css whenever styles.scss changes.

3. Final Answer:

   It watches styles.scss and updates styles.css on changes -> Option B

4. Quick Check:

   --watch updates CSS on SASS changes = C [OK]

Hint: Use --watch to auto-update CSS on SASS file changes [OK]

Common Mistakes:

• Thinking it compiles only once
• Confusing source and output files
• Assuming syntax error in correct command

4. You ran npm install -g sass but get a 'command not found' error when typing sass. What is the likely cause?

medium

A. You need to restart the terminal or add npm global bin to PATH

B. npm did not install sass globally

C. The sass package is deprecated and removed

D. You must run sass with 'node sass' command

Solution

1. Step 1: Understand global install effects

   Installing globally adds sass to a folder that must be in your system PATH to run from terminal.

2. Step 2: Identify common PATH issues

   If PATH is not updated or terminal not restarted, the system won't find the sass command.

3. Final Answer:

   You need to restart the terminal or add npm global bin to PATH -> Option A

4. Quick Check:

   PATH update needed after global install = A [OK]

Hint: Restart terminal or update PATH after global npm install [OK]

Common Mistakes:

• Assuming sass package is deprecated
• Trying to run sass with 'node sass'
• Thinking npm install failed without checking PATH

5. You want to automatically compile all SASS files in the src/sass folder into CSS files in dist/css folder whenever you save changes. Which command should you use?

hard

A. sass watch src/sass dist/css

B. sass src/sass dist/css --watch

C. sass --watch src/sass:dist/css

D. sass --watch src/sass/*.scss dist/css/*.css

Solution

1. Step 1: Understand folder watching syntax

   The syntax sass --watch input-folder:output-folder watches all SASS files in input-folder and compiles to output-folder.

2. Step 2: Evaluate each option

   sass --watch src/sass:dist/css uses correct syntax. Options A, B, and C have wrong order or invalid syntax.

3. Final Answer:

   sass --watch src/sass:dist/css -> Option C

4. Quick Check:

   Folder watch uses --watch input:output = D [OK]

Hint: Use --watch with folder paths separated by colon [OK]

Common Mistakes:

• Using spaces instead of colon between folders
• Trying to watch files with wildcards incorrectly
• Using 'sass watch' instead of 'sass --watch'