@kbach/react 1.0.0-beta.0 → 1.0.0-beta.10

package/dist/jsx-runtime.js

@@ -333,21 +333,54 @@ var defaultTheme = {
     ...PALETTE,
     surface: { light: "#f9fafb", dark: "#111827" }
   },
+  // Real Tailwind's default spacing scale in full — every step is exactly
+  // `n * 4px` (Tailwind's base spacing unit), including the fractional
+  // `.5` steps (`1.5` -> 6px, `2.5` -> 10px, `3.5` -> 14px) and the "px"
+  // literal (a bare 1px, for `p-px`-style hairline spacing). This table is
+  // only the "usual stops", though — the Rust/JS engines' shared
+  // `spacing_px`/`spacingPx` helper falls back to Tailwind v4's own live
+  // `n * 4px` formula for any bare numeric step NOT listed here (`p-0.25`,
+  // `gap-1.75`, `w-13`, ...), so this table exists to name the common
+  // values and give a theme customization something to override, not to
+  // enumerate every resolvable step. "px" is the one exception that must
+  // stay listed explicitly — it isn't a number, so the formula can't
+  // derive it.
   spacing: {
-    // "0" is always a hardcoded zero in real Tailwind's own scale too,
-    // regardless of the base spacing unit — needed for `p-0`/`m-0`/
-    // `top-0`/`inset-0`/etc., and specifically for `sticky top-0` (a
-    // sticky element needs an explicit offset to have any stick point at
-    // all; without one it behaves just like `relative`, no different from
-    // omitting `top-0` outright). Confirmed missing by hand: this
-    // sandbox's own header used `sticky top-0`, which silently never
-    // resolved (no "0" spacing key existed) until this was added.
     "0": 0,
+    "px": 1,
+    "0.5": 2,
     "1": 4,
+    "1.5": 6,
     "2": 8,
+    "2.5": 10,
+    "3": 12,
+    "3.5": 14,
     "4": 16,
+    "5": 20,
     "6": 24,
-    "8": 32
+    "7": 28,
+    "8": 32,
+    "9": 36,
+    "10": 40,
+    "11": 44,
+    "12": 48,
+    "14": 56,
+    "16": 64,
+    "20": 80,
+    "24": 96,
+    "28": 112,
+    "32": 128,
+    "36": 144,
+    "40": 160,
+    "44": 176,
+    "48": 192,
+    "52": 208,
+    "56": 224,
+    "60": 240,
+    "64": 256,
+    "72": 288,
+    "80": 320,
+    "96": 384
   },
   screens: {
     sm: 640,
@@ -356,7 +389,33 @@ var defaultTheme = {
     xl: 1280,
     "2xl": 1536
   },
-  darkMode: "attribute"
+  // Byte-for-byte the same three stacks
+  // packages/core-engine/src/resolvers/typography.rs's `font_family_value`
+  // falls back to — kept here too (rather than leaving this empty and
+  // relying purely on the Rust-side fallback) so `defaultTheme.fontFamily.sans`
+  // is a real, readable value for anything that wants to extend rather
+  // than replace it (see `KbachConfig.extend.fontFamily` in config.ts).
+  fontFamily: {
+    sans: 'ui-sans-serif, system-ui, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Noto Color Emoji"',
+    serif: 'ui-serif, Georgia, Cambria, "Times New Roman", Times, serif',
+    mono: 'ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, "Liberation Mono", "Courier New", monospace'
+  },
+  // Matches real Tailwind's own default (`darkMode: 'media'`): pure
+  // `@media (prefers-color-scheme: dark)`, works with zero JS — a project
+  // using only static `className` strings gets working `dark:` classes
+  // out of the box, with no runtime import required to write `data-theme`/
+  // `.dark` onto `<html>` (see darkModeStore.ts's `applyToDom`). The
+  // tradeoff: `'media'` can't be overridden by a manual light/dark toggle —
+  // `useTheme()`/`toggleGlobalDarkMode()` still track `isDark` correctly
+  // for JS consumers, but flipping it has no visible effect on `dark:`
+  // classes, since the browser's media query only ever reflects the real
+  // OS setting. Opt into `darkMode: 'class'` or `'attribute'` explicitly
+  // (via `kbach.config.js` or the `config`/`theme` plugin option) as soon
+  // as an app wants a real in-app toggle.
+  darkMode: "media",
+  // Empty by default, matching real Tailwind's own defaults (no forced
+  // centering/padding) — see `ContainerConfig`'s own doc comment.
+  container: {}
 };
 var activeThemeJson = JSON.stringify(defaultTheme);
 function getThemeJson() {

package/dist/jsx-runtime.mjs

@@ -2,9 +2,9 @@ import {
   Fragment,
   jsx,
   jsxs
-} from "./chunk-VBPQAIZL.mjs";
-import "./chunk-G3RJJNSY.mjs";
-import "./chunk-AFY36PRX.mjs";
+} from "./chunk-L6B4DTLD.mjs";
+import "./chunk-ROKZPEHA.mjs";
+import "./chunk-EOSN5CYG.mjs";
 export {
   Fragment,
   jsx,

package/dist/postcss-plugin.d.mts

@@ -0,0 +1,36 @@
+import { Plugin } from 'postcss';
+import { T as ThemeConfig, K as KbachConfig } from './config-BQ_b-qxF.mjs';
+
+interface KbachPostcssPluginOptions {
+    /**
+     * Project root to scan from. Defaults to `process.cwd()` — correct for
+     * the common case (PostCSS/Next.js run from the project root), but pass
+     * this explicitly if your `postcss.config.js` lives somewhere else, or
+     * from a monorepo app whose cwd differs from where `src`/`app` actually
+     * live.
+     */
+    root?: string;
+    /** Same as `KbachPluginOptions.theme` (vite-plugin/index.ts) — see its own doc comment. */
+    theme?: ThemeConfig;
+    /** Same as `KbachPluginOptions.config`. */
+    config?: KbachConfig;
+    /** Directories to scan for class strings, relative to `root`. Defaults to the same set the Vite plugin uses. */
+    include?: string[];
+    /** Same as `KbachPluginOptions.safelist`. */
+    safelist?: string[];
+}
+/**
+ * `postcss.config.js`:
+ * ```js
+ * module.exports = { plugins: { '@kbach/react/postcss': {} } };
+ * ```
+ * Processes whichever CSS file carries the `kbach:start`/`kbach:end`
+ * markers (conventionally `app/globals.css`/`src/kbach.css` — the same
+ * file you'd `@import`/reference like any other global stylesheet).
+ */
+declare function kbachPostcss(options?: KbachPostcssPluginOptions): Plugin;
+declare namespace kbachPostcss {
+    var postcss: boolean;
+}
+
+export { type KbachPostcssPluginOptions, kbachPostcss as default };

package/dist/postcss-plugin.d.ts

@@ -0,0 +1,36 @@
+import { Plugin } from 'postcss';
+import { T as ThemeConfig, K as KbachConfig } from './config-BQ_b-qxF.js';
+
+interface KbachPostcssPluginOptions {
+    /**
+     * Project root to scan from. Defaults to `process.cwd()` — correct for
+     * the common case (PostCSS/Next.js run from the project root), but pass
+     * this explicitly if your `postcss.config.js` lives somewhere else, or
+     * from a monorepo app whose cwd differs from where `src`/`app` actually
+     * live.
+     */
+    root?: string;
+    /** Same as `KbachPluginOptions.theme` (vite-plugin/index.ts) — see its own doc comment. */
+    theme?: ThemeConfig;
+    /** Same as `KbachPluginOptions.config`. */
+    config?: KbachConfig;
+    /** Directories to scan for class strings, relative to `root`. Defaults to the same set the Vite plugin uses. */
+    include?: string[];
+    /** Same as `KbachPluginOptions.safelist`. */
+    safelist?: string[];
+}
+/**
+ * `postcss.config.js`:
+ * ```js
+ * module.exports = { plugins: { '@kbach/react/postcss': {} } };
+ * ```
+ * Processes whichever CSS file carries the `kbach:start`/`kbach:end`
+ * markers (conventionally `app/globals.css`/`src/kbach.css` — the same
+ * file you'd `@import`/reference like any other global stylesheet).
+ */
+declare function kbachPostcss(options?: KbachPostcssPluginOptions): Plugin;
+declare namespace kbachPostcss {
+    var postcss: boolean;
+}
+
+export { type KbachPostcssPluginOptions, kbachPostcss as default };