Content configuration for tree-shaking in Tailwind - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is tree-shaking in Tailwind CSS?

Tree-shaking is a process that removes unused CSS styles from the final build, making the file smaller and faster to load.

beginner

Why do we need to configure the content option in Tailwind's config file?

The <code>content</code> option tells Tailwind where to look for class names in your files so it can keep only the styles you actually use.

intermediate

Which file types should you include in the content array for effective tree-shaking?

Include all files where you write Tailwind classes, like .html, .js, .jsx, .ts, .tsx, and .vue files.

intermediate

What happens if you forget to include some files in the content array?

Tailwind will remove styles used only in those files, causing your site to lose those styles and look broken.

beginner

How can you write the content array to include all HTML and JavaScript files in your project?

Use glob patterns like "./src/**/*.{html,js,jsx,ts,tsx,vue}" to include all files in the src folder and its subfolders.

What is the main purpose of the content option in Tailwind CSS config?

A To enable dark mode

B To set the color palette for the project

C To define custom fonts

D To specify where Tailwind looks for class names to keep

The content option tells Tailwind which files to scan for class names to include in the final CSS.

Which of these file patterns is best to include in the content array for React projects?

A ./src/**/*.{js,jsx,ts,tsx}

B ./src/**/*.{html,css}

C ./public/**/*.{html,js}

D ./styles/**/*.{css,scss}

React projects use JavaScript and TypeScript files with extensions like .js, .jsx, .ts, and .tsx where Tailwind classes are written.

What will happen if you include too many unrelated files in the content array?

A Tailwind will generate a larger CSS file with unused styles

B Tailwind will crash during build

C Tailwind will remove all styles

D Tailwind will ignore those files

Including unrelated files can cause Tailwind to keep unused styles, making the CSS file bigger.

Which of these is NOT a valid way to specify files in the content array?

A ./components/**/*.jsx

B ./src/**/*.{png,jpg}

C ./styles/*.css

D ./src/**/*.{html,js}

Images like .png and .jpg do not contain Tailwind classes, so including them in content is unnecessary.

Why is tree-shaking important for website performance?

A It adds more animations

B It changes colors automatically

C It reduces CSS file size, making pages load faster

D It disables unused JavaScript

Tree-shaking removes unused CSS, which reduces file size and speeds up page loading.

Explain how to configure the content option in Tailwind CSS for effective tree-shaking.

Think about where you write your Tailwind classes and how Tailwind finds them.

Describe what could go wrong if the content array is not set correctly in Tailwind CSS configuration.

Consider the impact on the website's look and performance.

Practice

1. What is the main purpose of the content configuration in Tailwind CSS?

easy

A. To tell Tailwind which files to scan for class names to include in the final CSS

B. To set the colors used in the Tailwind theme

C. To define custom animations in Tailwind

D. To specify the font sizes available in Tailwind

Solution

1. Step 1: Understand the role of content configuration

   The content setting tells Tailwind which files to look at for CSS class names.

2. Step 2: Identify the effect on CSS output

   By scanning these files, Tailwind can remove unused styles, making the CSS smaller and faster.

3. Final Answer:

   To tell Tailwind which files to scan for class names to include in the final CSS -> Option A

4. Quick Check:

   Content config = file paths for class scanning [OK]

Hint: Content config points to files Tailwind scans for classes [OK]

Common Mistakes:

• Confusing content with theme colors
• Thinking content sets animations or fonts
• Ignoring the importance of accurate file paths

2. Which of the following is the correct way to specify the content array in tailwind.config.js for scanning HTML and JS files in the src folder?

easy

A. content: ['./src/**/*.{html,js}']

B. content: './src/**/*.{html,js}'

C. content: ['./src/*.{html,js}']

D. content: ['./src/**/*.(html|js)']

Solution

1. Step 1: Understand the glob pattern syntax

   The pattern ./src/**/*.{html,js} means all files ending with .html or .js in any folder inside src.

2. Step 2: Check the array syntax

   The content property expects an array of strings, so it must be wrapped in [ ].

3. Final Answer:

   content: ['./src/**/*.{html,js}'] -> Option A

4. Quick Check:

   Array with glob pattern and braces = correct [OK]

Hint: Use array with glob and braces for multiple extensions [OK]

Common Mistakes:

• Forgetting the array brackets
• Using parentheses instead of braces in glob
• Missing the double asterisk for recursive search

3. Given this tailwind.config.js snippet:

module.exports = {
  content: ['./app/**/*.html'],
  theme: { extend: {} },
  plugins: [],
}

Which files will Tailwind scan for class names?

medium

A. Only HTML files directly inside the app folder

B. All HTML files inside the app folder and its subfolders

C. All files inside app folder with any extension

D. Only JavaScript files inside the app folder

Solution

1. Step 1: Analyze the glob pattern './app/**/*.html'

   The ** means any subfolder inside app, and *.html means all HTML files.

2. Step 2: Determine which files match

   So, Tailwind scans all HTML files in app and any nested folders.

3. Final Answer:

   All HTML files inside the app folder and its subfolders -> Option B

4. Quick Check:

   Double star + .html = all HTML recursively [OK]

Hint: Double star means recursive folders, *.html means HTML files [OK]

Common Mistakes:

• Thinking it scans only top-level files
• Assuming it scans all file types
• Confusing file extensions in pattern

4. You notice your Tailwind CSS file is very large and includes unused styles. Which of these is the most likely cause related to content configuration?

medium

A. You did not install the Tailwind plugin

B. You forgot to add @tailwind base; in your CSS

C. The content paths are missing or incorrect, so Tailwind scans no files

D. You used too many custom colors in the theme

Solution

1. Step 1: Understand tree-shaking in Tailwind

   Tailwind removes unused CSS by scanning files listed in content.

2. Step 2: Identify impact of wrong content paths

   If content is empty or wrong, Tailwind can't find used classes and keeps all styles.

3. Final Answer:

   The content paths are missing or incorrect, so Tailwind scans no files -> Option C

4. Quick Check:

   Wrong content paths = no tree-shaking [OK]

Hint: Check content paths if CSS is too big [OK]

Common Mistakes:

• Blaming CSS directives instead of content config
• Ignoring the importance of file paths
• Assuming plugins affect CSS size directly

5. You want to optimize your Tailwind CSS build by including only classes used in your React components inside src/components and your HTML files in public. Which content configuration is best?

hard

A. content: ['./src/**/*.{js,jsx,ts,tsx,html}', './public/**/*.{js,jsx}']

B. content: ['./src/components/*.js', './public/*.html']

C. content: ['./src/components/**/*', './public/**/*']

D. content: ['./src/components/**/*.{js,jsx,ts,tsx}', './public/**/*.html']

Solution

1. Step 1: Include all React component file types in src/components

   React components use extensions js, jsx, ts, tsx, so include these with a recursive glob.

2. Step 2: Include all HTML files in public folder recursively

   Use ./public/**/*.html to cover all HTML files in public and subfolders.

3. Step 3: Avoid overbroad or incomplete patterns

   content: ['./src/components/**/*.{js,jsx,ts,tsx}', './public/**/*.html'] precisely targets needed files without extra unrelated files.

4. Final Answer:

   content: ['./src/components/**/*.{js,jsx,ts,tsx}', './public/**/*.html'] -> Option D

5. Quick Check:

   Specific extensions + recursive glob = best practice [OK]

Hint: List exact file types and folders with recursive glob [OK]

Common Mistakes:

• Using too broad globs that include unused files
• Missing some React file extensions
• Not using recursive glob for nested files