Anatomie de tailwind.config.js
Comprenez chaque section du fichier de configuration, notamment content, theme, extend, plugins et presets, ainsi que leur influence sur la compilation.
Anatomie de tailwind.config.js est une leçon Tailwind CSS Academy gratuite sur CoddyKit. Ceci est la leçon 1 sur 4. Tu peux lire la leçon complète ci-dessous gratuitement — puis la pratiquer en direct dans le navigateur avec un éditeur de code intégré et un tuteur IA 24/7. Elle fait partie du parcours d'apprentissage Tailwind CSS Academy, et ta progression se synchronise sur le web et l'application CoddyKit. Le cours Tailwind CSS Academy comprend 4 leçons au total.
Certaines parties de cette leçon n'ont pas encore été traduites et s'affichent en anglais.
Why a Config File Exists
Tailwind CSS is designed to be customizable at its core. The tailwind.config.js file is the single source of truth for all customizations to the default design system. Without it, you get Tailwind's sensible defaults. With it, you can redefine any part of the design system — colors, fonts, spacing, breakpoints, animations, and more — while still generating the full utility class API automatically.
Generating the Config File
Create a default config file by running npx tailwindcss init. This generates a minimal tailwind.config.js with empty stubs for the most common sections. Use npx tailwindcss init --full to generate a complete config that includes every default value — useful for reference but usually too verbose to work with day-to-day.
# Generate a minimal config
npx tailwindcss init
# Generate a full config showing all defaults
npx tailwindcss init --full
# Generate config + postcss.config.js together
npx tailwindcss init -pThe content Section
The content array tells Tailwind where to look for class names so it can include only the utilities your project actually uses. You provide glob patterns pointing to your HTML, JS, JSX, TSX, Vue, and any other files that contain Tailwind classes. Getting this right is critical — missing a file means its classes get purged from the production build.
// tailwind.config.js
module.exports = {
content: [
'./src/**/*.{html,js,jsx,ts,tsx}',
'./pages/**/*.{js,jsx,ts,tsx}',
'./components/**/*.{js,jsx,ts,tsx}',
'./public/index.html',
],
// ...
};The theme Section
The theme section contains all design token configurations: colors, spacing, typography, breakpoints, shadows, border radii, and more. You can either extend the defaults (adding new values alongside existing ones) or override them (replacing defaults entirely). The theme object mirrors Tailwind's internal structure, where each key maps to a category of utilities.
// tailwind.config.js
module.exports = {
theme: {
// OVERRIDE: replaces ALL default font sizes
fontSize: {
sm: '0.875rem',
base: '1rem',
lg: '1.25rem',
},
extend: {
// EXTEND: adds TO the default font sizes
fontSize: {
'2xs': '0.625rem',
},
},
},
};The extend Key Explained
The theme.extend object is where you add custom values without replacing Tailwind's defaults. Anything inside extend is merged with the existing defaults rather than replacing them. This is the recommended approach for most projects — you keep everything Tailwind provides while adding your project-specific values on top. Reserve direct theme overrides for cases where you truly want to eliminate defaults.
// tailwind.config.js
module.exports = {
theme: {
extend: {
colors: {
brand: {
50: '#eff6ff',
500: '#3b82f6',
900: '#1e3a5f',
},
},
spacing: {
'128': '32rem',
'144': '36rem',
},
borderRadius: {
'4xl': '2rem',
},
},
},
};The plugins Section
The plugins array accepts official Tailwind plugins and custom plugins that extend the generated CSS. Plugins can add new utility classes, new component classes, new base styles, or new variants. You require them like any Node.js module and can pass configuration objects to plugins that support options. The plugins section runs after the theme is resolved, so plugins have access to all theme values.
// tailwind.config.js
const forms = require('@tailwindcss/forms');
const typography = require('@tailwindcss/typography');
module.exports = {
plugins: [
forms,
typography({ strategy: 'class' }),
require('@tailwindcss/aspect-ratio'),
],
};The presets Section
The presets array allows you to compose multiple Tailwind configurations together. A preset is just a Tailwind config object that serves as a base. Your project config is merged on top of it. This is the recommended pattern for sharing a base design system across multiple projects in a monorepo — define tokens once in a preset package and consume it everywhere.
// packages/ui-config/tailwind.preset.js
module.exports = {
theme: {
extend: {
colors: { brand: '#6366f1' },
},
},
};
// apps/my-app/tailwind.config.js
module.exports = {
presets: [require('@company/ui-config/tailwind.preset')],
content: ['./src/**/*.tsx'],
};The darkMode Setting
The darkMode key controls how Tailwind's dark: variant activates. Set it to 'media' to activate dark styles based on the OS preference, or 'class' to require a dark class on an ancestor. In Tailwind v3.3+, you can also pass an array with a custom selector: ['class', '.theme-dark'] to use a class name other than dark.
// tailwind.config.js
module.exports = {
darkMode: 'class', // or 'media', or ['class', '.theme-dark']
content: ['./src/**/*.{html,js}'],
theme: { extend: {} },
plugins: [],
};Config as ESM or CJS
By default, Tailwind expects a CommonJS module (module.exports). In projects using ESM (type: 'module' in package.json), name your config tailwind.config.cjs to explicitly use CommonJS syntax. Tailwind v4 (released 2024) moves to a CSS-first config approach entirely, but for v3 projects (still the most common), tailwind.config.js with CJS syntax is the standard.
// tailwind.config.cjs (for ESM projects)
/** @type {import('tailwindcss').Config} */
module.exports = {
content: ['./src/**/*.{html,js,jsx,ts,tsx}'],
theme: {
extend: {},
},
plugins: [],
};Using TypeScript Types in Config
Add a JSDoc @type annotation to your config file to get autocompletion in VSCode without converting to TypeScript. The type comes from the tailwindcss package itself. This tells your editor the exact shape of the config object, so you get autocomplete and type errors when you misspell a theme key or pass an invalid value.
// tailwind.config.js
/** @type {import('tailwindcss').Config} */
module.exports = {
content: ['./src/**/*.{html,js}'],
theme: {
extend: {
colors: {
primary: '#6366f1', // autocomplete shows available color keys
},
},
},
plugins: [],
};Config Sections at a Glance
To summarize the full anatomy of tailwind.config.js: content defines what files to scan, theme defines design tokens with extend for additive changes, plugins adds extended functionality, presets composes base configs, and darkMode controls dark variant behavior. Every section is optional — an empty config is valid and simply uses all of Tailwind's defaults.
// tailwind.config.js — full anatomy
module.exports = {
content: [], // file globs to scan
darkMode: 'class', // dark mode strategy
theme: {
// override defaults here
extend: {
// add to defaults here
},
},
plugins: [], // extend Tailwind's output
presets: [], // compose from base configs
};Quick Check
Test your understanding of the Tailwind CSS configuration file anatomy.
Lesson Recap
In this lesson you learned: the content array specifies which files to scan for class names, theme.extend adds values alongside defaults while direct theme overrides replace them, and plugins and presets compose and extend Tailwind's capabilities. Next up we explore content paths and how Tailwind purges unused classes in production.
Questions Fréquemment Posées
La leçon « Anatomie de tailwind.config.js » est-elle gratuite ?
Oui — le texte complet de « Anatomie de tailwind.config.js » est gratuit à lire ici sur le web. Pour la pratiquer de manière interactive (un éditeur de code intégré et un tuteur IA 24/7) et déverrouiller le reste du cours Tailwind CSS Academy, passe à CoddyKit PRO. Le cours Tailwind CSS Academy comprend 4 leçons au total.
Qu'est-ce que j'apprendrai dans « Anatomie de tailwind.config.js » ?
Comprenez chaque section du fichier de configuration, notamment content, theme, extend, plugins et presets, ainsi que leur influence sur la compilation. Tu pratiques Tailwind CSS Academy avec du code pratique que tu exécutes directement dans le navigateur, et un tuteur IA 24/7 répond à tes questions au fur et à mesure que tu avances dans la leçon.
Dois-je avoir de l'expérience pour commencer Tailwind CSS Academy ?
Aucune expérience préalable n'est requise. Tailwind CSS Academy sur CoddyKit est structuré pour les débutants jusqu'aux apprenants avancés, donc tu peux commencer ici ou depuis le début et avancer à ton rythme. Ceci est la leçon 1 sur 4.
Combien de temps prend la leçon « Anatomie de tailwind.config.js » ?
La plupart des leçons CoddyKit prennent environ 5–10 minutes. Chacune est courte et interactive, tu progresses régulièrement et tu repiques exactement où tu t'es arrêté sur le web et l'app.
Peux-tu écrire et exécuter du code dans cette leçon Tailwind CSS Academy ?
Oui. Chaque leçon Tailwind CSS Academy inclut un éditeur de code intégré, tu écris et exécutes du vrai code directement dans ton navigateur et tu reçois des retours IA instantanés — aucune configuration locale requise.
Toutes les leçons de ce cours
- Anatomie de tailwind.config.js
- Chemins de contenu et purge
- Étendre ou remplacer le thème
- Ajouter et configurer des plugins