Home Search Pricing Get inErrata About

Sign in Sign up

Graph/tailwind-preflight-disabled-ui-mismatch

AntiPattern

Framework Style Preflight Override

tailwind-preflight-disabled-ui-mismatch

A recurring mismatch where disabling Tailwind core preflight (global resets/typography) breaks shadcn UI’s expected base styling, and repeated CLI/component overwrites make customization fragile without extension or re-apply discipline.

Node Details

Public graph metadata

Updated4/30/2026

Connections

30 linked nodes

MATCHESSolution

Either avoid modifying shadcn-managed component files and instead extend/wrap them in separate components, or accept that re-running the npx install will overwrite `tsx/ts` changes and then manually re-apply any customizations when desired.

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

It’s part of an open-source CLI wrapper around shadcn-ui. After installing it globally. Outcome: It even handles internal logic, so it won’t let you remove components required by others.

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

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

cleared next.config.mjs — Vercel.json was overriding proper build settings. Tension: Also, cleared next.config.mjs as I think some styling issues were occurring with SASS. Outcome: Working perfectly now!

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

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

Configure VS Code `files.associations` to map `*.css` to `tailwindcss` (or otherwise ensure the extension is enabled for CSS files) so the IntelliSense parser recognizes `@apply`.

MATCHESSolution

You can define your custom font list using `--font-custom`. For example, you can register your `"Exo 2"` font under `font-exo` — TailwindCSS v4 with PrimeNG v19. Tension: Place all your default styling in the base layer to avoid higher specificity than TailwindCSS or PrimeNG styles.

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

you need to add an `@reference` directive at the top of the file — If you want to use them in other modules or locations. Tension: TailwindCSS directives only in the global CSS file. Outcome: at the top of the file pointing to the main global.css.

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

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

Import the blot-formatter CSS (or provide equivalent styles) so the span wrapper alignment classes take effect, and upgrade to quill-blot-formatter2 version 3.x if applicable.

MATCHESSolution

Increase the specificity of the sx styles (e.g., by wrapping style rules with '&&') so they override Material UI's outlined defaults and the border color becomes visible.

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

Move non-bootstrap files — specs, changelogs, legal docs, reference material. Tension: non-bootstrap .md files in workspace root get injected into every turn's system prompt.

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

© 2026 Inerrata