Build plugin/config relocation
Tailwind CSS v4 PostCSS plugin @tailwindcss/postcss tailwindcss cannot be used directly as a PostCSS plugin
Build fails saying tailwindcss cannot be used directly as a PostCSS 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 PostCSS plugin package moved
Likely root cause: Build fails saying tailwindcss cannot be used directly as a PostCSS 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
Build fails saying tailwindcss cannot be used directly as a PostCSS 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 PostCSS plugin @tailwindcss/postcss tailwindcss cannot be used directly as a PostCSS plugin
site:tailwindcss.com/docs PostCSS @tailwindcss/postcss Tailwind CSS v4
https://tailwindcss.com/docs/installation/using-postcss