@kolkrabbi/kol-theme 0.140.0 → 0.141.0
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.
- package/kol-design-tokens.css +42 -0
- package/package.json +1 -1
package/kol-design-tokens.css
CHANGED
|
@@ -209,4 +209,46 @@
|
|
|
209
209
|
--z-index-toast: var(--kol-z-toast);
|
|
210
210
|
--z-index-tooltip: var(--kol-z-tooltip);
|
|
211
211
|
--z-index-nav: var(--kol-z-nav);
|
|
212
|
+
|
|
213
|
+
/* SPACING (theme-does-not-register-spacing, kol-client-hrafn 2026-09-03).
|
|
214
|
+
* `--kol-spacing-*` was a real scale Tailwind could not see, so a consumer
|
|
215
|
+
* chose between `gap-[var(--kol-spacing-6)]` — 28 characters, and a
|
|
216
|
+
* `var(--kol-*)` read in JSX, which check 2 of the full-consumption contract
|
|
217
|
+
* flags — and `gap-6`, which is TAILWIND's number: identical today because
|
|
218
|
+
* both ladders are index × 4, and silently divergent the day KOL moves a
|
|
219
|
+
* step. hrafn swept 57 call sites twice in one session over exactly that.
|
|
220
|
+
*
|
|
221
|
+
* The indices already agree, so this is a no-op visually and a real change
|
|
222
|
+
* semantically: `p-4` now resolves THROUGH the KOL token, and a step that
|
|
223
|
+
* moves here moves everywhere.
|
|
224
|
+
*
|
|
225
|
+
* THE OFF-LADDER STEPS STILL GENERATE, deliberately. Tailwind v4's `--spacing`
|
|
226
|
+
* multiplier produces any numeric step on demand (`p-7`, `gap-1.5`), and the
|
|
227
|
+
* ticket asks for the gaps in the ladder (no 7, 9, 11…) to stop emitting.
|
|
228
|
+
* Measured before deciding: 130+ off-ladder utilities across this repo's own
|
|
229
|
+
* packages, kol-website, the clients, fxr, monitor and mirror — `gap-1.5` ×30,
|
|
230
|
+
* `py-1.5` ×24, `gap-0.5` ×18 alone. Killing the multiplier drops every one of
|
|
231
|
+
* them to NOTHING EMITTED, no error — the same silent failure this block was
|
|
232
|
+
* written to end for `z-modal`. Closing the ladder is a real ruling and it
|
|
233
|
+
* needs its own sweep, not a side effect of registering the scale. */
|
|
234
|
+
--spacing-1: var(--kol-spacing-1);
|
|
235
|
+
--spacing-2: var(--kol-spacing-2);
|
|
236
|
+
--spacing-3: var(--kol-spacing-3);
|
|
237
|
+
--spacing-4: var(--kol-spacing-4);
|
|
238
|
+
--spacing-5: var(--kol-spacing-5);
|
|
239
|
+
--spacing-6: var(--kol-spacing-6);
|
|
240
|
+
--spacing-8: var(--kol-spacing-8);
|
|
241
|
+
--spacing-10: var(--kol-spacing-10);
|
|
242
|
+
--spacing-12: var(--kol-spacing-12);
|
|
243
|
+
--spacing-16: var(--kol-spacing-16);
|
|
244
|
+
--spacing-20: var(--kol-spacing-20);
|
|
245
|
+
--spacing-24: var(--kol-spacing-24);
|
|
246
|
+
|
|
247
|
+
/* The two semantic steps a PAGE RAMP names, registered because they read as
|
|
248
|
+
* utilities (`py-section`, `px-container`). The three `--kol-spacing-gap-*`
|
|
249
|
+
* aliases stay CSS-only on purpose: `gap-gap-md` stutters, and `gap-md` would
|
|
250
|
+
* have to burn `--spacing-md`, a name too generic to spend on three values
|
|
251
|
+
* that are already `2` / `4` / `6`. */
|
|
252
|
+
--spacing-section: var(--kol-spacing-section);
|
|
253
|
+
--spacing-container: var(--kol-spacing-container);
|
|
212
254
|
}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@kolkrabbi/kol-theme",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.141.0",
|
|
4
4
|
"description": "KOL (Kolkrabbi) design-system tokens + base CSS — brand-neutral. The canonical token/cascade layer every other KOL package and consumer builds on.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"type": "module",
|