Creating custom utilities with addUtilities in Tailwind - Quick Revision & Summary

Recall & Review

beginner

What is the purpose of addUtilities in Tailwind CSS?

addUtilities lets you create your own custom CSS utility classes that work like Tailwind's built-in classes.

beginner

How do you define a simple custom utility for text-shadow using addUtilities?

<p>You create an object with the class name as key and CSS properties as value, then pass it to <code>addUtilities</code>.</p><pre>addUtilities({ '.text-shadow': { 'text-shadow': '2px 2px #000' } })</pre>

intermediate

Why should you include variants like hover or focus when adding utilities?

<p>Variants let your custom utilities respond to states like hover or focus, making your styles interactive and accessible.</p>

intermediate

Where do you place the addUtilities call in a Tailwind plugin?

Inside the plugin function, which Tailwind calls during build. You receive addUtilities as an argument to add your custom classes.

beginner

What is the benefit of using addUtilities over writing plain CSS?

It integrates your custom utilities into Tailwind's system, so you get consistent naming, responsive variants, and easy use in your HTML.

What argument does addUtilities expect?

A A string of CSS code

B A number representing pixel size

C An array of HTML elements

D An object with class names as keys and CSS properties as values

addUtilities expects an object where keys are class names and values are CSS property objects.

How do you add hover variants to your custom utilities?

A Pass a second argument with variants like <code>{ variants: ['hover'] }</code>

B Write <code>:hover</code> in the class name

C Use <code>addHoverUtilities</code> instead

D Hover variants are automatic and need no setup

You add variants by passing a second argument to addUtilities specifying which variants to generate.

Where do you write the code that calls addUtilities?

A Inside a Tailwind CSS plugin function

B In your HTML file

C In a JavaScript event listener

D In a CSS file

Custom utilities are added inside a Tailwind plugin function during the build process.

What is a benefit of using addUtilities for custom styles?

A They replace all default Tailwind utilities

B They integrate with Tailwind's responsive and state variants

C They automatically minify your CSS

D They only work in development mode

Custom utilities added with addUtilities can use Tailwind's variants like responsive and hover.

Which of these is a valid custom utility class using addUtilities?

A [ '.bg-stripes', { 'background-image': 'stripes' } ]

B { 'bg-stripes': 'background-image: stripes;' }

C { '.bg-stripes': { 'background-image': 'repeating-linear-gradient(45deg, #ccc, #ccc 10px, #fff 10px, #fff 20px)' } }

D '.bg-stripes { background-image: stripes; }'

The correct format is an object with class names as keys and CSS property objects as values.

Explain how to create a custom utility class in Tailwind CSS using addUtilities.

Think about how Tailwind builds its classes and how you can add your own.

Why is it useful to add variants when creating custom utilities with addUtilities?

Consider how users interact with elements on different devices and states.

Practice

1. What is the main purpose of using addUtilities in Tailwind CSS?

easy

A. To create custom CSS classes that can be reused in your HTML

B. To remove unused Tailwind CSS classes from the build

C. To automatically generate responsive breakpoints

D. To add JavaScript functionality to Tailwind components

Solution

1. Step 1: Understand the role of addUtilities

   addUtilities is used to define new CSS classes with custom styles that Tailwind does not provide by default.

2. Step 2: Compare with other options

   Options A, B, and D describe other Tailwind or unrelated features, not the purpose of addUtilities.

3. Final Answer:

   To create custom CSS classes that can be reused in your HTML -> Option A

4. Quick Check:

   addUtilities = create reusable custom classes [OK]

Hint: Remember: addUtilities adds new CSS classes [OK]

Common Mistakes:

• Confusing addUtilities with purge or remove features
• Thinking addUtilities adds JavaScript code
• Assuming it auto-generates responsive breakpoints

2. Which of the following is the correct syntax to add a custom utility class .text-shadow with text-shadow: 2px 2px #000; using addUtilities?

easy

A. addUtilities('.text-shadow { text-shadow: 2px 2px #000; }')

B. addUtilities({ '.text-shadow': { 'text-shadow': '2px 2px #000' } })

C. addUtilities({ textShadow: '2px 2px #000' })

D. addUtilities({ '.text-shadow': 'text-shadow: 2px 2px #000;' })

Solution

1. Step 1: Check the object format for addUtilities

   addUtilities expects an object where keys are class selectors and values are objects of CSS properties.

2. Step 2: Validate each option

   addUtilities({ '.text-shadow': { 'text-shadow': '2px 2px #000' } }) correctly uses an object with selector key and CSS property object value. Options B and D use incorrect formats (string or wrong value type). addUtilities({ textShadow: '2px 2px #000' }) misses the selector key.

3. Final Answer:

   addUtilities({ '.text-shadow': { 'text-shadow': '2px 2px #000' } }) -> Option B

4. Quick Check:

   addUtilities needs selector: CSS object [OK]

Hint: Use object with selector keys and CSS property objects [OK]

Common Mistakes:

• Passing CSS as a string instead of an object
• Omitting the selector key for the utility
• Using camelCase for CSS properties instead of kebab-case

3. Given this Tailwind plugin code snippet, what CSS class will be generated?

addUtilities({
  '.custom-border': {
    'border-width': '3px',
    'border-color': '#f00'
  }
})

medium

A. A class named .border-custom with 3px red border

B. A class named .custom-border with 1px black border

C. A class named .custom-border with 3px red border

D. No class will be generated due to syntax error

Solution

1. Step 1: Identify the class name and CSS properties

   The key '.custom-border' defines the class name. The CSS properties set border width to 3px and border color to red (#f00).

2. Step 2: Confirm no syntax errors

   The object syntax is correct, so the class will be generated as described.

3. Final Answer:

   A class named .custom-border with 3px red border -> Option C

4. Quick Check:

   Selector and CSS properties match output class [OK]

Hint: Class name is the object key, CSS inside is the style [OK]

Common Mistakes:

• Confusing class name with CSS property names
• Assuming default border width or color
• Thinking syntax error prevents generation

4. Identify the error in this Tailwind plugin code that tries to add a .bg-gradient utility:

addUtilities({
  '.bg-gradient': 'background: linear-gradient(to right, #000, #fff);'
})

medium

A. Missing semicolon after addUtilities call

B. Class selector should not start with a dot

C. The property name 'background' is invalid in Tailwind

D. CSS properties must be inside an object, not a string

Solution

1. Step 1: Check the value type for the class key

   The value for '.bg-gradient' must be an object with CSS properties, not a string.

2. Step 2: Validate other options

   Class selectors should start with a dot (correct here). 'background' is a valid CSS property. Semicolon after function call is optional in JavaScript.

3. Final Answer:

   CSS properties must be inside an object, not a string -> Option D

4. Quick Check:

   CSS properties need object format [OK]

Hint: Use object for CSS properties, not string [OK]

Common Mistakes:

• Passing CSS as a string instead of an object
• Removing the dot from class selector
• Thinking semicolon is mandatory after addUtilities

5. You want to create a custom utility .hover-scale that scales an element to 1.1 times its size on hover using addUtilities. Which is the correct way to add this utility with hover variant support?

hard

A. addUtilities({ '.hover-scale': { transform: 'scale(1.1)' } }, { variants: ['hover'] })

B. addUtilities({ '.hover-scale:hover': { transform: 'scale(1.1)' } })

C. addUtilities({ '.hover-scale': { ':hover': { transform: 'scale(1.1)' } } })

D. addUtilities({ '.hover-scale': { transform: 'scale(1.1)' } }, { variants: ['responsive'] })

Solution

1. Step 1: Understand how to add variants with addUtilities

   Variants like 'hover' are added as a second argument object with a variants array.

2. Step 2: Check each option's approach

   addUtilities({ '.hover-scale': { transform: 'scale(1.1)' } }, { variants: ['hover'] }) correctly adds the utility and enables hover variant. addUtilities({ '.hover-scale:hover': { transform: 'scale(1.1)' } }) incorrectly tries to put :hover in the selector key. addUtilities({ '.hover-scale': { ':hover': { transform: 'scale(1.1)' } } }) nests :hover inside CSS object, which is invalid. addUtilities({ '.hover-scale': { transform: 'scale(1.1)' } }, { variants: ['responsive'] }) uses 'responsive' variant, not hover.

3. Final Answer:

   addUtilities({ '.hover-scale': { transform: 'scale(1.1)' } }, { variants: ['hover'] }) -> Option A

4. Quick Check:

   Variants go in second argument as array [OK]

Hint: Add variants as second argument with variants array [OK]

Common Mistakes:

• Putting :hover inside selector string
• Nesting :hover inside CSS object
• Using wrong variant name like 'responsive' instead of 'hover'