Home Search Pricing Get inErrata About

Sign in Sign up

Graph/tailwind-config-drift

AntiPattern

Tailwind Config Drift

tailwind-config-drift

Tailwind behavior diverges from expectations after config changes because custom styles/utilities, theme tokens, and class generation aren’t wired correctly, so dark-mode transitions, theme color context, and typography utilities silently fail to apply.

Node Details

Public graph metadata

Updated7/1/2026

Connections

30 linked nodes

MATCHESSolution

TailwindCSS requires at least Node.js v20 to run — Knowing that I use Vite. Tension: LightningCSS will work. Outcome: Install the latest Microsoft Visual C++ Redistributable version.

MATCHESSolution

Use Tailwind v3 for shadcn/ui (e.g., install `tailwindcss@3` and follow the v3 init steps) or follow Tailwind v4’s official installation/init procedure instead of `npx tailwindcss init -p`.

MATCHESSolution

Try this with `import` — plugins: [require("tailwindcss-animate")],. Tension: require is not defined. Outcome: import * as tailwindAnimate from "tailwindcss-animate".

MATCHESSolution

Neither `ring-0` works, nor even `outline-none` — I am using a custom Tailwind button from Shadcn-UI in my React component. Tension: I am struggling to prevent the ugly ring that appears around the button when it comes in focus. Outcome: Even inline style as below (with `!important`, no less!), which I don’t want to depend on anyway, failed to do the job.

MATCHESSolution

To fix this, add a tailwind class `w-11/12` — when viewing on a phone. Tension: making the width not 100%. Outcome: Below is an example from the docs - I've added the class to show the example.

MATCHESSolution

Either replace `bg-dark-1` with an existing Tailwind background class (e.g., `bg-slate-950`) or define the custom color in `tailwind.config.js` (e.g., `theme.colors.dark[1] = '#...'`) so Tailwind generates the `bg-dark-1` utility.

MATCHESSolution

Rework the app to be HTML-first and framework-agnostic by using an HTML-rendered shadcn/ui implementation (e.g., franken-ui) that works with Tailwind, then use HTMX to request and swap HTML partials from the server to replace client-side JS behavior.

MATCHESSolution

webpack config. Tension: These two solutions can both fix this issue.

MATCHESSolution

Move shared Tailwind configuration into a reusable preset and reference/apply that preset from each app/package’s Tailwind config, ensuring the preset’s content scanning covers the relevant package files.

MATCHESSolution

body{ background-color: aqua !important; } — Maybe try using `!important` within the CSS. Tension: it always overrides the TailwindCSS code within my own code. Outcome: Only use the `!important` tag when you really need it.

MATCHESSolution

For breakpoints, you'd want to use the `--breakpoint-*` namespace in `@theme` — Tailwind v4. Outcome: You will get `max-*` variants generated for you automatically from these values.

MATCHESSolution

You can use an arbitrary variant — I’m using Tailwind CSS and I want to conditionally style a child element based on a class applied to the . Tension: open-modal:bg-red-800 doesn’t work since Tailwind doesn’t directly check for body classes like that. Outcome: You can use an arbitrary variant.

MATCHESSolution

it seems like you're trying to reference your `--spacing-my-custom-height-2` theme token. Tension: this is an invalid CSS value.

MATCHESSolution

I recommend declaring in advance which icons you need and building your component accordingly — When working with dynamic class names. Tension: Tailwind CSS requires a plugin to generate CSS for all possible class names first. Outcome: Don't construct class names dynamically.

MATCHESSolution

To avoid that, you must specify list of icon sets you want to use — with over 200,000 icons available. Tension: it might take a lot of time. Outcome: which might cause Tailwind CSS to run out of memory.

MATCHESSolution

Replace deprecated SCSS `@import` usage (e.g., `@import 'tailwindcss'`) with the recommended Tailwind/SCSS `@use`/proper import approach, and ensure styles are loaded once to prevent duplicate PrimeNG component instantiation.

MATCHESSolution

Use a small client component (e.g., Body) that reads the pathname with usePathname and applies the appropriate Tailwind/clsx class to the <body>, then wrap page content with this component in the shared root layout. This keeps the initial render correct (no flash) while enabling per-route background classes without layout groups.

MATCHESSolution

Use direct styles for the dynamic column span instead of Tailwind for this part

MATCHESSolution

Define the custom breakpoint using rem units (matching Tailwind’s defaults), e.g., set --breakpoint-xxl to an appropriate rem value, so breakpoint ordering and responsive utilities apply consistently.

MATCHESSolution

In Tailwind CSS, the @source directive is used to explicitly register source paths for Tailwind to scan for class names — add the following in `main.css`. Tension: This is also what official starter does. Outcome: @source "../../../content/**/*";.

MATCHESSolution

https://tailwindcss.com/docs/adding-custom-styles#adding-custom-utilities.

MATCHESSolution

Move the custom selectors into an appropriate Tailwind cascade layer (e.g., wrap .catpc and .catmobile in `@layer base` or `@layer components`) so Tailwind’s layers have the intended precedence. Alternatively, use Tailwind’s `@utility` directive for utility-like custom styles.

MATCHESSolution

To change the default theme, you need to set another theme as the default — @plugin "daisyui"{ themes: light, dark --prefersdark, cupcake --default; }. Tension: The light theme is perfect; it looks exactly as shown in the screenshot. Outcome: set cupcake as default.

MATCHESSolution

`field-sizing` utilities are not available in v3 — The `field-sizing` utilities was introduced in TailwindCSS v4. Tension: If you still want to use it with v3, you'll need to create your own custom class.

MATCHESSolution

Either migrate keyframes to the CSS-first approach using @theme { @keyframes ... } and define the animation variables there, or enable legacy configuration/backwards compatibility using the @config directive so tailwind.config.js is actually used.

MATCHESSolution

I found that the beta version of Daisy UI had a fix for this issue. Tension: There is no need to configure tailwind.config.js. Outcome: npm i -D tailwindcss@latest daisyui@beta.

MATCHESSolution

use styleobject instead of className when you have variable — when you have variable. Tension: remove `--turbo` flag from `next dev`. Outcome: Quick fix if you have a lot of variables.

MATCHESSolution

created a `.postcssrc.json` file instead of `postcss.config.[js|mjs]` — it solved it ! Outcome: { "plugins": { "@tailwindcss/postcss": {} } }.

MATCHESSolution

best practices for configuring devServer or devMiddleware — in future setups. Tension: prevent such vulnerabilities. Outcome: without upgrading the entire Vue CLI or webpack stack.

MATCHESSolution

delete your lock file and the node_modules folder, then reinstall version 1.7.3 — If that doesn't help, and if you are using React 18. Outcome: migrate the entire project to React 19 and use the new react-tailwindcss-datepicker v2 version.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata