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.
A child set to height: 100% collapses to its content size instead of filling the parent. Here's the containing-block rule causing it, the two things everyone tries first, and four real fixes.
[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? It's one of five causes: no top value, a clipping ancestor, a short parent, a stretched item, or html + body overflow. Fix each.
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.
Sass throws "Can't find stylesheet to import" even though the file exists. Case sensitivity, missing node_modules paths, and two more real causes, fixed one by one.
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.
Sass @import rules are deprecated, removed in Dart Sass 3.0.0. The exact warning, why your build still passes, and how to migrate to @use/@forward cleanly.
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.