JIT mode and on-demand generation in Tailwind - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does JIT stand for in Tailwind CSS?

JIT stands for Just-In-Time. It means Tailwind generates CSS styles only when they are needed, making the build faster and the CSS file smaller.

beginner

How does on-demand generation improve Tailwind CSS performance?

On-demand generation creates CSS classes only for the styles you use in your HTML or templates, reducing unused CSS and speeding up loading times.

intermediate

What is the main difference between Tailwind's JIT mode and the traditional build mode?

Traditional mode generates all possible CSS classes upfront, while JIT mode generates classes as you write them, making development faster and CSS smaller.

intermediate

How do you enable JIT mode in Tailwind CSS?

In Tailwind CSS v3 and later, JIT mode is enabled by default. For earlier versions, you add 'mode: "jit"' in the tailwind.config.js file.

beginner

Why is JIT mode helpful during development?

JIT mode gives instant feedback by generating styles as you type, so you see changes immediately without waiting for a full rebuild.

What happens when you use a new class in Tailwind CSS with JIT mode enabled?

A You must restart the build process to see the class.

B The CSS for that class is generated immediately.

C The class is ignored until manually added to CSS.

D All classes are generated at once regardless.

With JIT mode, Tailwind generates CSS for new classes as soon as you use them.

Which Tailwind CSS version has JIT mode enabled by default?

A v1.0

B v4.0

C v2.0

D v3.0

Tailwind CSS version 3.0 and later have JIT mode enabled by default.

What is a benefit of on-demand CSS generation?

A Larger CSS files

B Slower page load

C Smaller CSS files

D More unused styles

On-demand generation creates only the CSS you use, making files smaller.

How does JIT mode affect development speed?

A Speeds it up by generating styles instantly

B No effect on speed

C Slows it down due to full rebuilds

D Requires manual CSS updates

JIT mode speeds up development by generating styles instantly as you write code.

If you want to use a class not in your HTML, what must you do in JIT mode?

A Add it to the safelist in tailwind.config.js

B Nothing, it generates automatically

C Write it in a separate CSS file

D Restart the server

Classes not found in your files must be safelisted to be generated in JIT mode.

Explain how Tailwind CSS JIT mode works and why it is useful.

Think about when CSS classes are created and how that helps your workflow.

Describe the difference between traditional Tailwind CSS builds and JIT mode.

Focus on when CSS is generated in each mode.

Practice

1. What is the main benefit of Tailwind's JIT mode?

easy

A. It preloads all possible CSS classes to avoid delays.

B. It generates only the CSS classes you actually use, making the site faster.

C. It disables CSS generation to speed up development.

D. It automatically converts CSS to JavaScript.

Solution

1. Step 1: Understand JIT mode purpose

   JIT mode creates CSS only for classes used in your files, not all possible classes.

2. Step 2: Compare options

   It generates only the CSS classes you actually use, making the site faster. matches this behavior; others describe incorrect or unrelated features.

3. Final Answer:

   It generates only the CSS classes you actually use, making the site faster. -> Option B

4. Quick Check:

   JIT mode = on-demand CSS generation [OK]

Hint: JIT means generate CSS only when needed [OK]

Common Mistakes:

• Thinking JIT preloads all CSS
• Confusing JIT with disabling CSS
• Assuming JIT converts CSS to JS

2. Which Tailwind config snippet correctly enables JIT mode?

easy

A. module.exports = { mode: 'jit', paths: ['./src/**/*.{html,js}'] }

B. module.exports = { jit: true, files: ['./src/**/*.{html,js}'] }

C. module.exports = { mode: 'fast', content: ['./src/**/*.{html,js}'] }

D. module.exports = { mode: 'jit', content: ['./src/**/*.{html,js}'] }

Solution

1. Step 1: Identify correct config keys

   Tailwind uses mode: 'jit' and content array for files.

2. Step 2: Check options

   Only module.exports = { mode: 'jit', content: ['./src/**/*.{html,js}'] } uses correct keys and values; others use wrong keys or values.

3. Final Answer:

   module.exports = { mode: 'jit', content: ['./src/**/*.{html,js}'] } -> Option D

4. Quick Check:

   Config keys = mode and content [OK]

Hint: Use mode: 'jit' and content array in config [OK]

Common Mistakes:

• Using wrong keys like jit or files
• Setting mode to 'fast' instead of 'jit'
• Using 'paths' instead of 'content'

3. Given this Tailwind config with JIT mode:

module.exports = { mode: 'jit', content: ['./index.html'] }

And this HTML:

<div class="bg-blue-500 p-4">Hello</div>

What CSS classes will be generated?

medium

A. Only styles for bg-blue-500 and p-4 classes.

B. All background and padding classes from Tailwind.

C. No CSS classes because JIT is disabled.

D. Only bg-blue-500 class styles, not p-4.

Solution

1. Step 1: Understand JIT CSS generation

   JIT mode generates CSS only for classes found in the content files.

2. Step 2: Check classes in HTML

   Classes bg-blue-500 and p-4 appear, so their styles are generated.

3. Final Answer:

   Only styles for bg-blue-500 and p-4 classes. -> Option A

4. Quick Check:

   JIT generates CSS only for used classes [OK]

Hint: JIT generates CSS only for classes in your files [OK]

Common Mistakes:

• Thinking all classes generate CSS
• Assuming JIT disables CSS generation
• Believing partial classes generate partial CSS

4. You enabled JIT mode but your new CSS classes are not applying after editing HTML. What is the likely cause?

medium

A. JIT mode requires restarting the browser manually.

B. You forgot to install Tailwind CSS.

C. The content array in Tailwind config does not include the edited files.

D. Tailwind CSS does not support dynamic class names.

Solution

1. Step 1: Check JIT file watching setup

   JIT mode watches files listed in content to generate CSS on changes.

2. Step 2: Identify cause of missing CSS

   If edited files are not in content, JIT won't generate CSS for new classes.

3. Final Answer:

   The content array in Tailwind config does not include the edited files. -> Option C

4. Quick Check:

   Content array must include all source files [OK]

Hint: Always list all source files in content array [OK]

Common Mistakes:

• Forgetting to update content array
• Assuming JIT needs browser restart
• Thinking Tailwind lacks dynamic class support

5. You want to use a dynamic class name in your HTML like bg-${color}-500 where color is a variable. How can you ensure Tailwind JIT generates the correct CSS?

hard

A. Add all possible classes like bg-red-500, bg-blue-500 explicitly in your files or safelist in config.

B. JIT automatically detects dynamic class names and generates CSS for all variations.

C. Disable JIT mode to generate all CSS classes at once.

D. Use inline styles instead of Tailwind classes for dynamic colors.

Solution

1. Step 1: Understand JIT limitation with dynamic classes

   JIT cannot detect dynamic class names built from variables in code.

2. Step 2: Provide all possible classes explicitly

   You must list all possible class names in your files or use the safelist option in Tailwind config.

3. Final Answer:

   Add all possible classes like bg-red-500, bg-blue-500 explicitly in your files or safelist in config. -> Option A

4. Quick Check:

   Dynamic classes need explicit listing or safelist [OK]

Hint: List all dynamic classes or safelist them in config [OK]

Common Mistakes:

• Expecting JIT to detect dynamic classes automatically
• Disabling JIT unnecessarily
• Using inline styles instead of Tailwind classes