Conditional classes with clsx and twMerge in Tailwind - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the clsx function correctly.

Tailwind

import [1] from 'clsx';

Drag options to blanks, or click blank then click option'

AtwMerge

BclassNames

Cclsx

Dclassnames

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'classNames' or 'classnames' which are different libraries.

Confusing 'twMerge' with 'clsx'.

The clsx function is imported by its exact name clsx from the 'clsx' package.

2fill in blank

medium

Complete the code to conditionally add the bg-blue-500 class only when isActive is true.

Tailwind

const buttonClass = clsx('text-white', [1] && 'bg-blue-500');

Drag options to blanks, or click blank then click option'

AisActive

BhasError

CisLoading

DisDisabled

Attempts:

3 left

💡 Hint

Common Mistakes

Using unrelated variables like 'isDisabled' or 'hasError'.

Forgetting to use a condition and always applying the class.

The class bg-blue-500 should appear only if isActive is true, so we use isActive as the condition.

3fill in blank

hard

Fix the error in merging classes by completing the code to use twMerge correctly.

Tailwind

const mergedClasses = twMerge('p-4', [1], 'p-2');

Drag options to blanks, or click blank then click option'

Aclsx('p-6')

Bclsx('p-2')

Cclsx('p-8')

Dclsx('p-4')

Attempts:

3 left

💡 Hint

Common Mistakes

Passing plain strings instead of using clsx.

Using conflicting padding classes without merging.

Using clsx('p-4') merges with other classes, and twMerge will resolve conflicting padding classes, keeping the last one.

4fill in blank

hard

Fill both blanks to create a class string that conditionally adds text-red-500 if hasError is true and merges with baseClasses.

Tailwind

const classes = twMerge(baseClasses, clsx([1] && 'text-red-500', [2] && 'bg-blue-500'));

Drag options to blanks, or click blank then click option'

AhasError

BisActive

CisDisabled

Dloading

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up the variables for error and active states.

Not using conditions properly inside clsx.

The first blank should be hasError to conditionally add the red text class. The second blank is isActive to add any other conditional classes if needed.

5fill in blank

hard

Fill all three blanks to create a merged class string that includes uppercase text if isUppercase is true, adds padding p-4, and conditionally adds bg-green-500 if isSuccess is true.

Tailwind

const finalClass = twMerge(clsx([1] && 'uppercase'), [2], clsx([3] && 'bg-green-500'));

Drag options to blanks, or click blank then click option'

AisUppercase

B'p-4'

CisSuccess

DisError

Attempts:

3 left

💡 Hint

Common Mistakes

Using variables instead of string for padding.

Mixing up success and error variables.

The first blank is isUppercase to conditionally add uppercase text. The second blank is the padding string 'p-4'. The third blank is isSuccess to conditionally add the green background.

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