CDN vs build tool comparison in Tailwind - Hands-On Comparison

CDN vs Build Tool Comparison

📖 Scenario: You want to start a new project using Tailwind CSS. You need to decide between using the CDN for quick setup or installing Tailwind with a build tool for full power. You will try both approaches to understand the difference.

🎯 Goal: Set up Tailwind CSS using both the CDN method and the build tool method, then compare the output to understand why production projects use build tools.

📋 What You'll Learn

Create an HTML page using Tailwind via CDN

Set up Tailwind with npm and the CLI build tool

Compare the generated CSS file sizes

Demonstrate a feature only available with build tools

💡 Why This Matters

🌍 Real World

Every production Tailwind project uses build tools. CDN is only for learning and quick demos.

💼 Career

Interviewers expect you to know the difference and when to use each approach.

1

Create HTML page with Tailwind CDN

Create an index-cdn.html file that loads Tailwind CSS from the CDN and uses a few utility classes to style a heading and button.

Tailwind

Hint

Add <script src="https://cdn.tailwindcss.com"></script> in the head section.

2

Initialize Tailwind with npm

In a new project folder, run npm init -y, install Tailwind CSS as a dev dependency, and generate the config file with npx tailwindcss init.

Tailwind

# Terminal commands:
# Step 1: Initialize npm project
# Step 2: Install tailwindcss
# Step 3: Generate config file

Hint

Use npm install -D tailwindcss to install as a dev dependency, then npx tailwindcss init to create tailwind.config.js.

3

Configure content paths and create input CSS

Update tailwind.config.js to scan your HTML files, and create an input.css file with the three Tailwind directives.

Tailwind

// tailwind.config.js
module.exports = {
  content: [/* Add your content paths here */],
  theme: { extend: {} },
  plugins: [],
}

/* input.css */
/* Add the three Tailwind directives here */

Hint

Set content to ['./*.html'] so Tailwind scans your HTML files for used classes.

4

Build and compare output sizes

Run the Tailwind CLI to compile your CSS, then create the same styled page using the build output instead of the CDN. Add a custom color using theme.extend to demonstrate a build-tool-only feature.

Tailwind

// tailwind.config.js — add a custom color
module.exports = {
  content: ['./*.html'],
  theme: {
    extend: {
      // Add custom color here
    }
  },
  plugins: [],
}

// Terminal: build command
// npx tailwindcss -i input.css -o output.css --minify

Hint

Add a colors object inside extend with your custom color name and hex value.

Practice

1. Which of the following is a key advantage of using Tailwind via CDN instead of a build tool?

easy

A. It produces a smaller, optimized CSS file for production.

B. It automatically removes unused CSS classes.

C. It allows custom configuration of Tailwind classes.

D. It requires no setup and works immediately for quick prototypes.

Solution

1. Step 1: Understand CDN usage context

   Using Tailwind via CDN means you just add a link to your HTML and start using styles immediately without setup.

2. Step 2: Compare with build tool features

   Build tools require setup but optimize CSS size and allow customization, unlike CDN which loads all styles.

3. Final Answer:

   It requires no setup and works immediately for quick prototypes. -> Option D

4. Quick Check:

   CDN = No setup, fast start [OK]

Hint: CDN means no setup, build tool means setup and optimization [OK]

Common Mistakes:

• Thinking CDN optimizes CSS size
• Assuming CDN allows custom config
• Believing CDN removes unused styles

2. Which HTML tag correctly includes Tailwind CSS via CDN?

easy

A.

B.

C.

D.

Solution

1. Step 1: Identify correct CDN inclusion method

   Tailwind CDN is included via a script tag that loads the Tailwind JavaScript to inject styles dynamically.

2. Step 2: Eliminate incorrect tags

   Link tag is for CSS files, but Tailwind CDN uses a script. Style tag cannot have src attribute. Custom tags like <tailwind> are invalid.

3. Final Answer:

   <script src="https://cdn.tailwindcss.com"></script> -> Option A

4. Quick Check:

   Tailwind CDN uses <script> tag [OK]

Hint: Tailwind CDN loads via script tag, not link [OK]

Common Mistakes:

• Using <link> instead of <script>
• Adding src to <style> tag
• Using non-standard HTML tags

3. Given this Tailwind setup using CDN:

<script src="https://cdn.tailwindcss.com"></script>
<div class="text-red-500 p-4">Hello</div>

What will be the color and padding of the div?

medium

A. Text color red, no padding

B. Text color red, padding 1rem

C. Default text color, padding 1rem

D. Default text color, no padding

Solution

1. Step 1: Understand Tailwind CDN effect

   The CDN loads all Tailwind styles, so all utility classes like text-red-500 and p-4 are available.

2. Step 2: Interpret class meanings

   text-red-500 sets text color to a shade of red, p-4 sets padding to 1rem (16px by default).

3. Final Answer:

   Text color red, padding 1rem -> Option B

4. Quick Check:

   text-red-500 + p-4 = red text + 1rem padding [OK]

Hint: CDN loads full styles, so all classes work as expected [OK]

Common Mistakes:

• Assuming CDN misses some classes
• Confusing padding units
• Thinking CDN disables styles

4. A developer uses Tailwind via build tool but notices the CSS file is very large and slow to load. What is the most likely cause?

medium

A. They included Tailwind CSS twice in the HTML.

B. They used the CDN method instead of build tool.

C. They forgot to configure PurgeCSS or content paths to remove unused styles.

D. They used outdated Tailwind version.

Solution

1. Step 1: Understand build tool optimization

   Build tools rely on PurgeCSS or content scanning to remove unused CSS classes and reduce file size.

2. Step 2: Identify cause of large CSS

   If PurgeCSS or content paths are not configured, the build tool includes all Tailwind styles, making the CSS large.

3. Final Answer:

   They forgot to configure PurgeCSS or content paths to remove unused styles. -> Option C

4. Quick Check:

   Missing purge config = large CSS [OK]

Hint: Build tool needs purge config to shrink CSS [OK]

Common Mistakes:

• Confusing CDN with build tool issues
• Assuming version affects CSS size directly
• Ignoring duplicate CSS includes

5. You are designing a scalable web app that uses Tailwind CSS. Which approach is best for production to optimize performance and maintainability?

hard

A. Use a build tool with proper purge configuration to generate optimized CSS.

B. Use inline styles instead of Tailwind classes.

C. Include the entire Tailwind CSS file manually in the project.

D. Use Tailwind via CDN for all pages to avoid build setup.

Solution

1. Step 1: Consider scalability and performance needs

   For scalable apps, loading only needed CSS reduces file size and speeds up loading.

2. Step 2: Evaluate Tailwind methods

   Build tools with purge remove unused styles, creating small CSS files. CDN loads full CSS, which is large and inefficient for production.

3. Step 3: Assess maintainability

   Build tools allow custom config and integration with development workflow, improving maintainability.

4. Final Answer:

   Use a build tool with proper purge configuration to generate optimized CSS. -> Option A

5. Quick Check:

   Build tool + purge = optimized, scalable CSS [OK]

Hint: Build tool with purge is best for production [OK]

Common Mistakes:

• Choosing CDN for production
• Manually including full CSS
• Using inline styles over utility classes