Content configuration for tree-shaking in Tailwind - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is content configuration important for Tailwind CSS tree-shaking?

Tailwind CSS removes unused styles during build to reduce file size. Why must you configure the content option correctly?

A To specify the colors Tailwind should use in the project.

B To tell Tailwind which files to scan for class names so it keeps only used styles.

C To define the font sizes Tailwind will generate in the CSS.

D To set the screen sizes for responsive design.

💡 Hint

Think about how Tailwind knows which CSS classes you actually use in your files.

The content option tells Tailwind which files to scan for class names. This helps Tailwind keep only the CSS classes you use, removing unused styles and making your CSS smaller.

📝 Syntax

intermediate

Which content configuration correctly includes all HTML and JS files in the src folder?

Choose the correct content array for Tailwind config to scan all HTML and JS files inside src/ and its subfolders.

A ["./src/**/*.(html|js)"]

B ["./src/*.{html,js}"]

C ["./src/**/.*.{html,js}"]

D ["./src/**/*.{html,js}"]

💡 Hint

Remember the correct glob pattern syntax for matching multiple file extensions.

The pattern ./src/**/*.{html,js} matches all files ending with .html or .js in src and any subfolder. Option D misses subfolders, A uses wrong syntax, and D looks for hidden files.

❓ rendering

advanced

What happens if you omit the content configuration in Tailwind CSS?

Consider a Tailwind project with no content paths set in tailwind.config.js. What will the generated CSS file contain?

A The CSS file will include all Tailwind styles, making it very large.

B The CSS file will include only default colors but no utilities.

C The CSS file will be empty because no files are scanned.

D The build will fail with an error about missing content paths.

💡 Hint

Think about what Tailwind does when it does not know which classes you use.

If no content paths are set, Tailwind generates an empty CSS file because no files are scanned for used classes.

❓ selector

advanced

Which content pattern excludes node_modules but includes JSX files in src?

Choose the content array that scans all JSX files in src/ but excludes node_modules folder.

A ["./src/**/*.{jsx}", "!./node_modules/**/*"]

B ["./src/**/*.jsx"]

C ["./src/**/*.{jsx}", "./node_modules"]

D ["./src/**/*.{jsx}", "!./node_modules"]

💡 Hint

How do you exclude a folder in glob patterns?

Option A correctly includes all JSX files in src and excludes all files inside node_modules using the negation pattern !./node_modules/**/*. Option A excludes node_modules folder itself but not its contents, B does not explicitly exclude node_modules, and C explicitly includes node_modules.

❓ accessibility

expert

How does proper content configuration improve accessibility indirectly?

Why can correct content configuration in Tailwind CSS help improve accessibility of your website?

A By reducing CSS file size, pages load faster, improving user experience for all including assistive tech users.

B By disabling animations that cause motion sickness.

C By generating keyboard navigation styles by default.

D By automatically adding ARIA labels to all elements.

💡 Hint

Think about how performance affects accessibility.

Proper content configuration enables Tailwind to remove unused CSS, making files smaller and pages load faster. Faster loading improves accessibility for users with slow connections or assistive technologies.

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