FG
💻 Software🌐 Web & Full-Stack

"@tailwindcss/vite": "4.0.8" and "@tailwindcss/vite": "4.0.9" have massively increased load times for the CSS in Vite.

Fresh12 months ago
Mar 14, 20260 views
Confidence Score86%
86%

Problem

So I have noticed drastically increased load times when using Vite and Tailwind when updating to "@tailwindcss/vite": "4.0.8" and "@tailwindcss/vite": "4.0.9". "@tailwindcss/vite": "4.0.8" and "@tailwindcss/vite": "4.0.9" <img width="1331" alt="Image" src="https://github.com/user-attachments/assets/9b284158-be5f-4a4b-994e-ed3b4624befa" /> "@tailwindcss/vite": "4.0.7" and lower. <img width="1421" alt="Image" src="https://github.com/user-attachments/assets/b76206e7-effb-4d97-9583-77a5be53937e" /> Not sure what is causing this. Happy to share more information about my setup or debug further with instructions. Thanks

Unverified for your environment

Select your OS to check compatibility.

1 Fix

Canonical Fix
Moderate Confidence Fix
84% confidence100% success rate2 verificationsLast verified Mar 14, 2026

Solution: "@tailwindcss/vite": "4.0.8" and "@tailwindcss/vite": "4.0.9" have massively increased load times for the CSS in Vite.

Low Risk

Encountering similar issue with a React project (using `react-router` v7 as framework), temp workaround for us is to downgrade and pin both `tailwindcss` and `@tailwindcss/vite` to `4.0.7` EDIT (2025-03-07T19:32:52+0000) Pinning the build slowdown to `"@tailwindcss/vite": "4.0.10"`, while `tailwindcss` itself can be updated to `4.0.12` without any issue. So theoretically having `"tailwindcss": "^

84

Trust Score

2 verifications

100% success
  1. 1

    Encountering similar issue with a React project (using `react-router` v7 as fram

    Encountering similar issue with a React project (using `react-router` v7 as framework), temp workaround for us is to downgrade and pin both `tailwindcss` and `@tailwindcss/vite` to `4.0.7`

  2. 2

    EDIT (2025-03-07T19:32:52+0000)

    Pinning the build slowdown to `"@tailwindcss/vite": "4.0.10"`, while `tailwindcss` itself can be updated to `4.0.12` without any issue. So theoretically having `"tailwindcss": "^4.0.12"` and `"@tailwindcss/vite": "4.0.9"` builds okay.

  3. 3

    EDIT (2025-03-10T14:31:05+0000)

    Some CPU profile highlighting the difference

Validation

Resolved in tailwindlabs/tailwindcss GitHub issue #16911. Community reactions: 1 upvotes.

Verification Summary

Worked: 2
Last verified Mar 14, 2026

Sign in to verify this fix

Environment

Submitted by

AC

Alex Chen

2450 rep

Tags

tailwindcsscssneeds-reproduction