Conditional classes with clsx and twMerge in Tailwind - Mini Project: Build & Apply

Conditional classes with clsx and twMerge

📖 Scenario: You are building a simple button component for a website. The button should look different when it is active or disabled. You will use Tailwind CSS classes to style the button. To manage the classes easily, you will use the clsx library to add classes conditionally and twMerge to combine classes without duplicates.

🎯 Goal: Create a button with conditional Tailwind CSS classes using clsx and twMerge. The button should have a base style, an active style when isActive is true, and a disabled style when isDisabled is true. Use clsx to add classes based on these conditions and twMerge to merge them properly.

📋 What You'll Learn

Create a base set of Tailwind CSS classes for the button.

Create two boolean variables: isActive and isDisabled.

Use clsx to conditionally add classes based on isActive and isDisabled.

Use twMerge to merge the classes into one string.

Render a button element with the merged class string.

💡 Why This Matters

🌍 Real World

Buttons with different states are everywhere on websites. Using clsx and twMerge helps keep the code clean and easy to manage when styles change based on state.

💼 Career

Understanding how to conditionally apply Tailwind CSS classes with clsx and twMerge is a valuable skill for frontend developers working with React and Tailwind CSS.

1

Set up base button classes

Create a constant called baseClasses and set it to the string "px-4 py-2 rounded font-semibold text-white" which will be the base Tailwind CSS classes for the button.

Tailwind

# Create a constant called baseClasses with the base Tailwind CSS classes
# Your code here

Hint

Think of the base button style as the basic look that all buttons share.

2

Add boolean variables for state

Create two constants: isActive set to true and isDisabled set to false. These will control the button's state.

Tailwind

const baseClasses = "px-4 py-2 rounded font-semibold text-white";
// Create isActive and isDisabled constants
# Your code here

Hint

Use const to create these boolean variables exactly as named.

3

Use clsx to add conditional classes

Import clsx and create a constant called conditionalClasses that uses clsx to add "bg-blue-500" if isActive is true, and "bg-gray-400 cursor-not-allowed" if isDisabled is true.

Tailwind

import clsx from 'clsx';

const baseClasses = "px-4 py-2 rounded font-semibold text-white";
const isActive = true;
const isDisabled = false;

// Create conditionalClasses using clsx with conditions
# Your code here

Hint

Use an object inside clsx where keys are class strings and values are conditions.

4

Merge classes with twMerge and render button

Import twMerge from tailwind-merge. Create a constant called finalClasses that merges baseClasses and conditionalClasses using twMerge. Then write a JSX <button> element with className set to finalClasses and text content Click me.

Tailwind

import clsx from 'clsx';
import { twMerge } from 'tailwind-merge';

const baseClasses = "px-4 py-2 rounded font-semibold text-white";
const isActive = true;
const isDisabled = false;

const conditionalClasses = clsx({
  "bg-blue-500": isActive,
  "bg-gray-400 cursor-not-allowed": isDisabled
});

// Merge classes with twMerge and render button
# Your code here

Hint

Use twMerge to combine the base and conditional classes into one string without duplicates. Then use that string in the button's className.

Practice

1. What is the main purpose of using clsx in a Tailwind CSS project?

easy

A. To conditionally combine multiple class names into one string

B. To automatically generate Tailwind CSS classes

C. To minify CSS files for faster loading

D. To replace Tailwind CSS with custom styles

Solution

1. Step 1: Understand clsx functionality

   clsx is a utility that helps combine class names conditionally, making it easier to apply classes based on logic.

2. Step 2: Compare options

   Only To conditionally combine multiple class names into one string correctly describes clsx's purpose. Other options describe unrelated tasks.

3. Final Answer:

   To conditionally combine multiple class names into one string -> Option A

4. Quick Check:

   clsx combines classes conditionally = C [OK]

Hint: clsx joins classes based on conditions, like a smart list builder [OK]

Common Mistakes:

• Thinking clsx generates CSS classes
• Confusing clsx with CSS minifiers
• Assuming clsx replaces Tailwind CSS

2. Which of the following is the correct syntax to use clsx to conditionally add the class bg-blue-500 only when isActive is true?

easy

A. clsx('bg-blue-500' && isActive)

B. clsx({ 'bg-blue-500': isActive })

C. clsx('bg-blue-500' || isActive)

D. clsx(bg-blue-500: isActive)

Solution

1. Step 1: Recall clsx conditional syntax

   clsx accepts an object where keys are class names and values are booleans to include or exclude classes.

2. Step 2: Analyze each option

   clsx({ 'bg-blue-500': isActive }) uses the correct object syntax. Options B and C misuse logical operators, and D has invalid syntax.

3. Final Answer:

   clsx({ 'bg-blue-500': isActive }) -> Option B

4. Quick Check:

   clsx uses object with class:condition = A [OK]

Hint: Use object syntax { 'class-name': condition } with clsx [OK]

Common Mistakes:

• Using logical operators inside clsx incorrectly
• Missing quotes around class names
• Writing invalid object syntax

3. Given the code snippet:

import clsx from 'clsx';
import { twMerge } from 'tailwind-merge';

const isPrimary = true;
const isDisabled = false;

const buttonClass = twMerge(clsx('px-4 py-2', {
  'bg-blue-500': isPrimary,
  'bg-gray-400': !isPrimary,
  'opacity-50 cursor-not-allowed': isDisabled
}));

console.log(buttonClass);

What will be printed in the console?

medium

A. "px-4 py-2 bg-blue-500"

B. "px-4 py-2 bg-gray-400 opacity-50 cursor-not-allowed"

C. "px-4 py-2 bg-blue-500 opacity-50 cursor-not-allowed"

D. "px-4 py-2 bg-gray-400"

Solution

1. Step 1: Evaluate clsx conditions

   isPrimary is true, so 'bg-blue-500' is included; !isPrimary is false, so 'bg-gray-400' is excluded; isDisabled is false, so 'opacity-50 cursor-not-allowed' is excluded.

2. Step 2: Apply twMerge

   twMerge cleans conflicting classes but here only 'bg-blue-500' is present, so no conflicts to resolve.

3. Final Answer:

   "px-4 py-2 bg-blue-500" -> Option A

4. Quick Check:

   clsx + twMerge output = "px-4 py-2 bg-blue-500" [OK]

Hint: Check boolean flags carefully, then apply twMerge to clean conflicts [OK]

Common Mistakes:

• Including classes with false conditions
• Ignoring twMerge effect on conflicting classes
• Mixing up true/false conditions

4. Identify the error in this code snippet using clsx and twMerge:

const isActive = true;
const classes = twMerge(clsx('text-white', {
  'bg-red-500': isActive,
  'bg-green-500' isActive === false
}));
console.log(classes);

medium

A. isActive variable is not defined

B. Using twMerge incorrectly without importing

C. clsx cannot accept objects as arguments

D. Missing comma between object properties inside clsx

Solution

1. Step 1: Check object syntax inside clsx

   Inside the object, properties must be separated by commas. The line 'bg-green-500' isActive === false lacks a comma after the first property.

2. Step 2: Verify other parts

   twMerge usage is correct assuming import exists, clsx accepts objects, and isActive is defined.

3. Final Answer:

   Missing comma between object properties inside clsx -> Option D

4. Quick Check:

   Object properties need commas = D [OK]

Hint: Check commas between object properties in clsx [OK]

Common Mistakes:

• Forgetting commas between object keys
• Assuming clsx can't take objects
• Ignoring variable definitions

5. You want to create a button that is bg-red-500 when error is true, bg-green-500 when success is true, and bg-gray-300 otherwise. Using clsx and twMerge, which code correctly applies these classes without conflicts?

hard

A. twMerge(clsx('px-4 py-2', {
'bg-red-500': error,
'bg-green-500': success,
'bg-gray-300': !error && !success
}))

B. clsx(twMerge('px-4 py-2'), {
'bg-red-500': error,
'bg-green-500': success,
'bg-gray-300': !error && !success
})

C. twMerge(clsx('px-4 py-2', error ? 'bg-red-500' : success ? 'bg-green-500' : 'bg-gray-300'))

D. clsx('px-4 py-2', error && 'bg-red-500', success && 'bg-green-500', !error && !success && 'bg-gray-300')

Solution

1. Step 1: Understand class conflicts

   Only one background color class should be applied at a time to avoid conflicts.

2. Step 2: Analyze each option

   twMerge(clsx('px-4 py-2', { 'bg-red-500': error, 'bg-green-500': success, 'bg-gray-300': !error && !success })) uses clsx with multiple conditional classes that can conflict; twMerge will merge but logic is less clear. twMerge(clsx('px-4 py-2', error ? 'bg-red-500' : success ? 'bg-green-500' : 'bg-gray-300')) uses nested ternary to pick exactly one class, then twMerge cleans up. clsx(twMerge('px-4 py-2'), { 'bg-red-500': error, 'bg-green-500': success, 'bg-gray-300': !error && !success }) misuses clsx and twMerge order. clsx('px-4 py-2', error && 'bg-red-500', success && 'bg-green-500', !error && !success && 'bg-gray-300') uses clsx but may add multiple bg classes simultaneously.

3. Step 3: Choose best practice

   twMerge(clsx('px-4 py-2', error ? 'bg-red-500' : success ? 'bg-green-500' : 'bg-gray-300')) cleanly selects one bg class and uses twMerge properly.

4. Final Answer:

   twMerge(clsx('px-4 py-2', error ? 'bg-red-500' : success ? 'bg-green-500' : 'bg-gray-300')) -> Option C

5. Quick Check:

   Use ternary for exclusive classes + twMerge = B [OK]

Hint: Use ternary to pick one class, then twMerge to clean conflicts [OK]

Common Mistakes:

• Applying multiple conflicting bg classes at once
• Wrong order of clsx and twMerge calls
• Not ensuring only one bg class is active