SASS with PostCSS pipeline - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is SASS in web development?

SASS is a CSS preprocessor that lets you write styles using variables, nested rules, and functions to make CSS easier to manage and reuse.

beginner

What role does PostCSS play in a CSS build pipeline?

PostCSS processes CSS with plugins to add features like autoprefixing, minification, and compatibility fixes after SASS compiles CSS.

intermediate

Why combine SASS and PostCSS in a pipeline?

Combining SASS and PostCSS lets you write advanced styles with SASS features, then optimize and enhance the CSS output with PostCSS plugins for better browser support and performance.

beginner

Name a common PostCSS plugin used after SASS compilation.

Autoprefixer is a common PostCSS plugin that adds vendor prefixes to CSS rules to ensure compatibility across different browsers.

intermediate

What is the typical order of processing in a SASS with PostCSS pipeline?

First, SASS compiles .scss files into plain CSS. Then, PostCSS processes that CSS with plugins like Autoprefixer or cssnano to optimize and enhance the styles.

What does SASS primarily add to CSS?

A Variables and nesting

B JavaScript functionality

C Database connectivity

D Image optimization

SASS adds features like variables and nested rules to make CSS easier to write and maintain.

Which PostCSS plugin automatically adds vendor prefixes?

A Prettier

B cssnano

C Stylelint

D Autoprefixer

Autoprefixer scans CSS and adds necessary vendor prefixes for browser compatibility.

In a SASS with PostCSS pipeline, when is PostCSS run?

A Before SASS compilation

B At the same time as SASS

C After SASS compilation

D PostCSS is not used with SASS

PostCSS processes the CSS output after SASS compiles the SCSS files.

Which of these is NOT a benefit of using PostCSS after SASS?

A Adding vendor prefixes

B Writing variables

C Minifying CSS

D Fixing browser bugs

Writing variables is a SASS feature, not something PostCSS adds.

What file extension do SASS source files usually have?

A .scss

B .html

C .js

D .css

SASS source files typically use the .scss extension.

Explain how SASS and PostCSS work together in a CSS build pipeline.

Think about the order and purpose of each tool.

List common PostCSS plugins used after SASS and describe their purpose.

Focus on plugins that optimize CSS after SASS compilation.

Practice

1. What is the main role of PostCSS in a SASS with PostCSS pipeline?

easy

A. To compile SASS code into CSS

B. To process compiled CSS and add browser prefixes automatically

C. To write variables and nesting in styles

D. To minify JavaScript files

Solution

1. Step 1: Understand the role of SASS

   SASS is a preprocessor that lets you write CSS with variables and nesting, but it does not add browser prefixes.

2. Step 2: Understand the role of PostCSS

   PostCSS processes the compiled CSS to add features like browser prefixes automatically, improving browser compatibility.

3. Final Answer:

   To process compiled CSS and add browser prefixes automatically -> Option B

4. Quick Check:

   PostCSS adds prefixes after SASS compiles CSS [OK]

Hint: PostCSS works on CSS output, not on SASS source [OK]

Common Mistakes:

• Confusing SASS compilation with PostCSS processing
• Thinking PostCSS compiles SASS
• Assuming PostCSS writes variables

2. Which of the following is the correct order to use SASS and PostCSS in a build pipeline?

easy

A. Compile SASS first, then run PostCSS

B. Only run SASS, PostCSS is optional

C. Run both simultaneously

D. Run PostCSS first, then compile SASS

Solution

1. Step 1: Identify the output of SASS

   SASS compiles .scss files into plain CSS files.

2. Step 2: Understand PostCSS input requirements

   PostCSS works on CSS files, so it must run after SASS compilation.

3. Final Answer:

   Compile SASS first, then run PostCSS -> Option A

4. Quick Check:

   SASS compiles, PostCSS processes CSS [OK]

Hint: Compile SASS before PostCSS to process CSS output [OK]

Common Mistakes:

• Running PostCSS before SASS compilation
• Trying to run both at the same time
• Skipping PostCSS thinking it's unnecessary

3. Given this SASS code and PostCSS with autoprefixer, what will be the final CSS output?

$color: blue;
.button {
  color: $color;
  display: flex;
}

medium

A. .button { color: blue; display: -webkit-box; display: -ms-flexbox; display: flex; }

B. .button { color: blue; display: flex; }

C. .button { color: $color; display: flex; }

D. .button { color: blue; display: block; }

Solution

1. Step 1: Compile SASS variables and nesting

   The variable $color is replaced with blue, so color: blue; is output.

2. Step 2: PostCSS autoprefixer adds vendor prefixes

   For display: flex;, autoprefixer adds -webkit-box and -ms-flexbox prefixes for browser support.

3. Final Answer:

   .button { color: blue; display: -webkit-box; display: -ms-flexbox; display: flex; } -> Option A

4. Quick Check:

   SASS compiles variables, PostCSS adds prefixes [OK]

Hint: SASS compiles variables; PostCSS adds prefixes like -webkit- [OK]

Common Mistakes:

• Leaving SASS variables uncompiled
• Ignoring vendor prefixes added by PostCSS
• Replacing flex with block incorrectly

4. You wrote this SASS code but your PostCSS autoprefixer is not adding prefixes. What is the likely problem?

$main-color: red;
.container {
  color: $main-color;
  display: flex;
}

medium

A. PostCSS does not support autoprefixer

B. You used wrong variable syntax in SASS

C. You forgot to compile SASS before running PostCSS

D. You need to write prefixes manually in SASS

Solution

1. Step 1: Check SASS compilation step

   If SASS is not compiled first, PostCSS receives raw SASS code and cannot add prefixes.

2. Step 2: Confirm PostCSS autoprefixer usage

   PostCSS autoprefixer works on CSS, so it requires compiled CSS input.

3. Final Answer:

   You forgot to compile SASS before running PostCSS -> Option C

4. Quick Check:

   Compile SASS before PostCSS for prefixes [OK]

Hint: Always compile SASS before PostCSS to enable prefixing [OK]

Common Mistakes:

• Running PostCSS on uncompiled SASS
• Assuming autoprefixer works on SASS syntax
• Thinking prefixes must be written manually

5. You want to create a responsive button style using SASS variables and PostCSS autoprefixer. Which approach correctly combines both tools?

// SASS variables
$btn-color: green;

// SASS nested styles
.button {
  color: $btn-color;
  display: flex;
  &:hover {
    color: darkgreen;
  }
}

// PostCSS autoprefixer runs after SASS compilation

hard

A. Use only PostCSS autoprefixer without SASS for variables

B. Write CSS with prefixes manually, then run SASS compiler

C. Run PostCSS autoprefixer on SASS files before compiling

D. Write SASS with variables and nesting, compile it, then run PostCSS autoprefixer to add prefixes

Solution

1. Step 1: Use SASS for variables and nesting

   SASS lets you write variables and nested styles for cleaner CSS.

2. Step 2: Compile SASS to CSS, then run PostCSS autoprefixer

   PostCSS autoprefixer adds vendor prefixes after SASS compilation for browser support.

3. Final Answer:

   Write SASS with variables and nesting, compile it, then run PostCSS autoprefixer to add prefixes -> Option D

4. Quick Check:

   SASS for structure, PostCSS for prefixes [OK]

Hint: Write SASS first, then autoprefix CSS with PostCSS [OK]

Common Mistakes:

• Running autoprefixer before SASS compilation
• Writing prefixes manually instead of using PostCSS
• Skipping SASS variables and nesting