Preset sharing across projects in Tailwind - Performance & Optimization

Performance: Preset sharing across projects

MEDIUM IMPACT

This affects the build time and bundle size by reusing shared Tailwind configurations across projects.

Sharing Tailwind configuration presets across multiple projects

Tailwind

/* Create a shared preset package with common Tailwind config */
// shared-preset/index.js
module.exports = {
  theme: {
    extend: {
      colors: {
        brand: '#123456'
      }
    }
  },
  plugins: []
};

// In each project tailwind.config.js
const sharedPreset = require('shared-preset');
module.exports = {
  presets: [sharedPreset],
  theme: {
    extend: {
      spacing: {
        '72': '18rem'
      }
    }
  }
};

Using a shared preset avoids duplicating config, so Tailwind generates CSS once and reuses it.

📈 Performance GainReduces build time and CSS bundle size by sharing common styles.

Sharing Tailwind configuration presets across multiple projects

Tailwind

/* Each project has its own full tailwind.config.js with duplicated settings */
module.exports = {
  theme: {
    extend: {
      colors: {
        brand: '#123456'
      }
    }
  },
  plugins: []
};

Duplicating the same Tailwind config in every project causes repeated CSS generation and larger bundles.

📉 Performance CostIncreases build time and adds redundant CSS to each project bundle.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Duplicated Tailwind configs per project	No change	No change	Higher due to larger CSS	[X] Bad
Shared Tailwind preset across projects	No change	No change	Lower due to smaller CSS	[OK] Good

Rendering Pipeline

Tailwind presets affect the CSS generation step before the browser rendering pipeline. Efficient presets reduce CSS size, which speeds up style calculation and paint in the browser.

→Style Calculation

→Layout

→Paint

⚠️ BottleneckStyle Calculation due to large CSS files

Core Web Vital Affected

LCP

This affects the build time and bundle size by reusing shared Tailwind configurations across projects.

Optimization Tips

1Use shared Tailwind presets to avoid duplicating config across projects.

2Smaller CSS bundles improve Largest Contentful Paint (LCP).

3Check CSS file size in DevTools Network tab to measure impact.

Performance Quiz - 3 Questions

What is the main performance benefit of sharing Tailwind presets across projects?

A Increases CSS specificity for better styling

B Reduces duplicated CSS and build time

C Adds more plugins to Tailwind config

D Improves JavaScript execution speed

DevTools: Network

How to check: Open DevTools > Network tab, reload page, filter by CSS files, and compare CSS file sizes.

What to look for: Smaller CSS file size indicates effective preset sharing and less redundant CSS.

Practice

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

easy

A. To create custom CSS animations

B. To share common Tailwind settings across multiple projects

C. To add new color palettes only for one project

D. To compile Tailwind CSS faster on a single project

Solution

1. Step 1: Understand the role of presets

   Presets are used to share configuration settings like colors, fonts, and plugins across projects.

2. Step 2: Compare options

   Options B, C, and D describe features unrelated to sharing configs across projects.

3. Final Answer:

   To share common Tailwind settings across multiple projects -> Option B

4. Quick Check:

   Presets = Shared config across projects [OK]

Hint: Presets = shared config for multiple projects [OK]

Common Mistakes:

• Thinking presets only add colors or animations
• Confusing presets with plugins
• Believing presets speed up compilation

2. Which of the following is the correct way to include a preset in tailwind.config.js?

easy

A. presets: require('tailwind-preset')

B. presets: ['tailwind-preset']

C. presets: [require('tailwind-preset')]

D. preset: [require('tailwind-preset')]

Solution

1. Step 1: Check the correct property name and syntax

   The property is presets (plural) and it expects an array of required modules.

2. Step 2: Validate each option

   presets: [require('tailwind-preset')] uses presets with an array containing require('tailwind-preset'), which is correct syntax.

3. Final Answer:

   presets: [require('tailwind-preset')] -> Option C

4. Quick Check:

   Presets property + array + require() = correct [OK]

Hint: Use presets as an array with require() inside [OK]

Common Mistakes:

• Using singular 'preset' instead of 'presets'
• Not wrapping require() inside an array
• Passing string instead of require()

3. Given this tailwind.config.js snippet, what will be the background color of a div with class bg-primary?

module.exports = {
  presets: [require('./shared-preset')],
  theme: {
    extend: {
      colors: {
        primary: '#ff0000'
      }
    }
  }
}

And the shared-preset.js contains:

module.exports = {
  theme: {
    colors: {
      primary: '#00ff00'
    }
  }
}

medium

A. #ff0000 (red) from local config

B. No color applied, class invalid

C. #00ff00 (green) from preset

D. Error due to conflicting colors

Solution

1. Step 1: Understand config merging order

   Local config overrides preset values when keys conflict, so local primary color '#ff0000' overrides preset '#00ff00'.

2. Step 2: Determine final color for bg-primary

   The div uses the local config color '#ff0000' (red).

3. Final Answer:

   #ff0000 (red) from local config -> Option A

4. Quick Check:

   Local config overrides preset colors [OK]

Hint: Local theme colors override preset colors [OK]

Common Mistakes:

• Assuming preset colors override local config
• Thinking conflicting keys cause errors
• Believing class won't apply without explicit import

4. You added a preset in tailwind.config.js but your styles from the preset are not applying. What is the most likely mistake?

medium

A. Using preset instead of presets in config

B. Forgetting to export the preset module with module.exports

C. Not installing Tailwind CSS in the project

D. Adding presets inside the theme object

Solution

1. Step 1: Check common config mistakes

   Using preset (singular) instead of presets (plural) means Tailwind ignores the preset array.

2. Step 2: Validate other options

   Forgetting to export the preset module with module.exports is possible but less common; C and D are unrelated to preset loading.

3. Final Answer:

   Using preset instead of presets in config -> Option A

4. Quick Check:

   Correct property name is 'presets' [OK]

Hint: Use 'presets' plural, not 'preset' singular [OK]

Common Mistakes:

• Misspelling 'presets' as 'preset'
• Placing presets inside wrong config section
• Not exporting preset module properly

5. You want to share a preset that includes custom fonts and colors across three projects. Which approach ensures all projects use the preset and can override colors if needed?

hard

A. Use Tailwind's CDN link with custom fonts and colors embedded

B. Copy the preset config file into each project and import it manually in CSS files

C. Write the preset config directly inside each project's tailwind.config.js without sharing

D. Create a separate npm package with the preset and add it in each project's presets array; override colors locally as needed

Solution

1. Step 1: Identify best sharing method

   Creating a separate npm package for the preset allows easy reuse and updates across projects.

2. Step 2: Confirm override capability

   Adding the preset in presets array lets each project override colors locally without changing the shared preset.

3. Final Answer:

   Create a separate npm package with the preset and add it in each project's presets array; override colors locally as needed -> Option D

4. Quick Check:

   npm package + presets array + local overrides = best practice [OK]

Hint: Use npm package for preset + local overrides [OK]

Common Mistakes:

• Copying preset files manually causing duplication
• Embedding config directly without sharing
• Using CDN which can't share config presets