Ajouter et configurer des plugins

Tailwind plugins extend the generated CSS by adding new utility classes, component classes, base styles, or variant modifiers. Unlike modifying the config's theme section (which only changes design token values), plugins can add entirely new CSS rules, selectors, and even new class families. Official plugins from the Tailwind team cover common needs like typography and forms, while the community provides hundreds more.

The Tailwind team maintains four first-party plugins, each solving a specific problem that falls outside the core utility classes. @tailwindcss/typography styles rich HTML content from markdown. @tailwindcss/forms resets browser form styles for easier customization. @tailwindcss/aspect-ratio adds aspect ratio utilities for older browsers. @tailwindcss/container-queries adds container query support as utility classes.

Plugins are registered in the plugins array of tailwind.config.js. Simply require() the plugin and add it to the array. Plugins without configuration options are added directly. Plugins that accept options are called as functions with a configuration object. Multiple plugins can coexist in the same array without conflict.

The @tailwindcss/typography plugin adds a prose class (and its variants) that applies beautiful typographic styles to raw HTML content — like rendered markdown from a CMS or blog. Apply prose to a container and all its descendant elements (headings, paragraphs, lists, code blocks, blockquotes) get styled automatically without adding classes to each individual element.

The typography plugin is configurable both through the plugin options and through the Tailwind theme. Use strategy: 'class' to only apply prose styles when the prose class is explicitly added (as opposed to base styles). Customize the prose scale (sm, base, lg, xl, 2xl) and override specific element styles through the theme.typography key in your config.

The @tailwindcss/forms plugin resets the default browser styles for form elements like inputs, selects, textareas, checkboxes, and radio buttons. Without it, different browsers render these controls completely differently. With it, all form elements get a consistent, minimal baseline style that Tailwind utilities can then enhance. Choose strategy: 'class' to opt into the resets per element rather than globally.

CSS container queries let components respond to the size of their parent container rather than the viewport. The @tailwindcss/container-queries plugin adds @container marking and @sm:, @md:, @lg: responsive prefixes that work like breakpoints but relative to the nearest container. This is powerful for building truly reusable components that adapt to any context they are placed in.

Beyond official plugins, a rich ecosystem of community plugins extends Tailwind with animation libraries, scrollbar utilities, grid patterns, and more. Popular examples include tailwindcss-animate for CSS animations (used by shadcn/ui), tailwind-scrollbar for scrollbar styling, and @headlessui/tailwindcss for Headless UI state variants. Research plugins before adding them — check download counts, maintenance status, and bundle impact.

You can write a custom plugin inline inside the plugins array using Tailwind's plugin function from the tailwindcss/plugin module. This is useful for adding a small set of custom utilities or components without creating a separate file. The plugin function receives a helper object with addUtilities, addComponents, addBase, and addVariant methods.

Plugins are applied in the order they appear in the array. If two plugins add utilities with the same class name, the later plugin wins. Be aware that plugins using addBase inject styles into Tailwind's base layer, which may interact with existing reset styles. Test for conflicts after adding multiple plugins by inspecting the compiled CSS for unexpected overrides or duplicate declarations.

After adding a plugin, verify it is working by checking that its classes appear in your compiled CSS and apply correctly in the browser. For the typography plugin, add the prose class to a content element and inspect the applied styles. For forms, check that input elements have the normalized baseline appearance. If classes from the plugin are absent, ensure the plugin is listed in the correct plugins array and the package is installed.

Test your understanding of adding and configuring Tailwind plugins.

In this lesson you learned: Tailwind plugins are registered in the plugins array of the config, the four official plugins cover typography, forms, aspect ratio, and container queries, and you can write inline plugins using the plugin() helper for custom utilities. Next up we explore adding custom colors, fonts, and spacing to your Tailwind project.