Build plugin/config relocation
Tailwind CSS v4 upgrade guide @tailwind base components utilities @import "tailwindcss"
CSS builds without fatal error but utility classes are absent.
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 old @tailwind directives produce no styles
Likely root cause: CSS builds without fatal error but utility classes are absent.
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
CSS builds without fatal error but utility classes are absent.
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 upgrade guide @tailwind base components utilities @import "tailwindcss"
site:tailwindcss.com/docs/upgrade-guide v4 @tailwind utilities @import "tailwindcss"
https://tailwindcss.com/docs/upgrade-guide