opsfuse-ui 0.1.7 → 0.1.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -65,9 +65,11 @@ For **Next.js App Router** add it first in `app/layout.tsx`; for **Pages Router*
65
65
 
66
66
  **One bundle, every Tailwind version.** `styles.css` is a single precompiled, self-contained bundle that works on Tailwind v3, v4, and future hosts — there is nothing to choose. (`styles.layered.css` still exists as an identical backward-compat alias; prefer `styles.css`.) You do not run Tailwind over it.
67
67
 
68
- **Import it _before_ your own CSS — this is the one rule that matters.** The library wraps all its CSS in a single low-priority `@layer opsfuse`. Imported first, your host Tailwind registers later, so on a **v4 host** its layers win and on a **v3 host** its un-layered utilities win — either way your `className` overrides on library components (`md:px-8`, `bg-red-500`, hover/responsive variants) stay authoritative. The library's design tokens, themed borders, and heading typography are emitted un-layered + scoped to `.opsfuse-ui`, so they survive your host's preflight without leaking into or overriding the rest of your app.
68
+ **Import it _before_ your own CSS — this is the one rule that matters.** The bundle is fully **flat** (no cascade layers) and entirely **scoped to `.opsfuse-ui`**: its component utilities are single classes that out-specify your host's bare-element preflight (`*{…}`), so library components render with their intended borders, rings, sidebar states, etc. on **both** v3 and v4 — they can't be wiped by your host's reset. Library base resets use `:where(.opsfuse-ui)` (zero specificity), so your own utility classes still win. Importing first means equal-specificity ties resolve in your favor.
69
69
 
70
- > The bundle ships **no global preflight** — it never restyles your `html`, `body`, headings, or form controls. A scoped equivalent applies only inside `.opsfuse-ui`, so component normalization is intact with zero document-level side effects.
70
+ > The bundle ships **no global preflight** and no global `:root` palette — it never restyles your `html`, `body`, headings, form controls, or your Tailwind theme. A scoped equivalent applies only inside `.opsfuse-ui`, so component normalization is intact with zero document-level side effects.
71
+
72
+ > **Overrides:** because library utilities are un-layered, a host can't override a component purely through cascade layers. Override per-component via `className` instead — the library merges it with `cn()` / tailwind-merge, which drops the conflicting class so your value wins cleanly. (This requires components to live inside `<OpsfuseThemeProvider>`, which applies the `.opsfuse-ui` scope the tokens depend on.)
71
73
 
72
74
  ### 2b. Font setup
73
75