Build plugin/config relocation
Tailwind CSS v4 Vite plugin @tailwindcss/vite official docs
HMR/build behavior is slow or broken because the project misses the dedicated Vite plugin.
Agent Quick Fix
Repair against the current Tailwind CSS contract, then keep the change narrow and source-backed.
Product: Tailwind CSS
Current-contract area: Tailwind v4 Vite integration still uses PostCSS path
Likely root cause: HMR/build behavior is slow or broken because the project misses the dedicated Vite plugin.
Repair direction: Verifier checks the current package identity/config format and a real transformed output. Verify a minimal current configuration and actual generated CSS.Symptom
HMR/build behavior is slow or broken because the project misses the dedicated Vite plugin.
Why This Happens
The old package/config name is syntactically valid, but current tool packaging and discovery rules live in external release documentation.
Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
Tailwind CSS v4 Vite plugin @tailwindcss/vite official docs
site:tailwindcss.com/docs/installation/using-vite @tailwindcss/vite
https://tailwindcss.com/docs/installation/using-vite