Why your Tailwind classes aren't showing up
The class is right there in the DOM and nothing happens. Here's why Tailwind never saw it, and four fixes that actually hold up in production.
The class is right there in the DOM and nothing happens. Here's why Tailwind never saw it, and four fixes that actually hold up in production.
[postcss] It looks like you're trying to use `tailwindcss` directly as a PostCSS plugin. Every cause of this Tailwind v4 error, plus the silent one that hits next.
Position: sticky not working? Six causes ranked by how often they bite: a missing top, an overflow ancestor, flex stretch, a short parent, and one console snippet that finds it.
Your Tailwind v4 upgrade throws 'trying to use tailwindcss directly as a PostCSS plugin'? Here's every cause, the sneaky CI-only variant, and the real fix.
The class is sitting right there in your JSX and the browser still ignores it. Here's why Tailwind's scanner can't see it, and how to fix it for good.
Your Tailwind v4 build dies with 'It looks like you're trying to use tailwindcss directly as a PostCSS plugin': here's every real cause and the actual fix.
[postcss] It looks like you're trying to use `tailwindcss` directly as a PostCSS plugin. Every cause of this Tailwind v4 error, plus the silent one that hits next.