@kbach/react 1.0.0-beta.4 → 1.0.0-beta.6

package/dist/postcss-plugin.mjs

@@ -0,0 +1,79 @@
+import {
+  DEFAULT_SCAN_DIRS,
+  createKbachStaticCssEngine,
+  resolveEffectiveTheme
+} from "./chunk-GPLCUNFX.mjs";
+import "./chunk-NKR3PSWO.mjs";
+import "./chunk-N5HCQIBB.mjs";
+
+// src/postcss-plugin/index.ts
+import postcss from "postcss";
+import { resolve as resolvePath } from "path";
+var KBACH_START_TEXT = "kbach:start";
+var KBACH_END_TEXT = "kbach:end";
+function isKbachMarker(node, text) {
+  return !!node && node.type === "comment" && node.text === text;
+}
+function spliceGeneratedCss(root, generatedCss) {
+  const nodes = root.nodes;
+  let startIdx = -1;
+  let endIdx = -1;
+  for (let i = 0; i < nodes.length; i++) {
+    if (startIdx === -1 && isKbachMarker(nodes[i], KBACH_START_TEXT)) {
+      startIdx = i;
+      continue;
+    }
+    if (startIdx !== -1 && isKbachMarker(nodes[i], KBACH_END_TEXT)) {
+      endIdx = i;
+      break;
+    }
+  }
+  if (startIdx === -1 || endIdx === -1) {
+    console.warn(
+      `[kbach] postcss plugin: no "/* kbach:start */" / "/* kbach:end */" marker pair found \u2014 add both to the file this plugin processes (see @kbach/react/vite's own convention). Nothing was generated.`
+    );
+    return;
+  }
+  for (const stale of nodes.slice(startIdx + 1, endIdx)) stale.remove();
+  const parsed = postcss.parse(generatedCss);
+  const newNodes = [...parsed.nodes];
+  let after = nodes[startIdx];
+  for (const node of newNodes) {
+    root.insertAfter(after, node);
+    after = node;
+  }
+}
+function kbachPostcss(options = {}) {
+  return {
+    postcssPlugin: "kbach",
+    Once(root, { result }) {
+      const projectRoot = options.root ?? process.cwd();
+      const theme = resolveEffectiveTheme(projectRoot, options);
+      const includeDirs = options.include ?? DEFAULT_SCAN_DIRS;
+      const safelist = options.safelist ?? [];
+      const engine = createKbachStaticCssEngine({
+        root: projectRoot,
+        theme,
+        themeJson: JSON.stringify(theme),
+        includeDirs,
+        safelist
+      });
+      engine.scanProjectCssSelectorsOnce();
+      engine.initialScan();
+      engine.processSafelist();
+      for (const dir of includeDirs) {
+        result.messages.push({
+          type: "dir-dependency",
+          plugin: "kbach",
+          dir: resolvePath(projectRoot, dir),
+          glob: "**/*"
+        });
+      }
+      spliceGeneratedCss(root, engine.generateCSS());
+    }
+  };
+}
+kbachPostcss.postcss = true;
+export {
+  kbachPostcss as default
+};

package/dist/vite-plugin.d.mts

@@ -28,6 +28,36 @@ interface KbachPluginOptions {
      */
     safelist?: string[];
 }
+declare const DEFAULT_SCAN_DIRS: string[];
+declare const CSS_SYNC_DEBOUNCE_MS = 50;
+/**
+ * Auto-discovers `kbach.config.js` at the project root — `undefined` if it
+ * doesn't exist (the common case: most projects have no customization at
+ * all, so this is a silent, expected no-op, not a warning).
+ *
+ * Uses `require()` (a real project's `kbach.config.js` is plain CommonJS,
+ * `module.exports = {...}`, matching every example in this package's own
+ * README), built via `createRequire(root)` rather than
+ * `createRequire(import.meta.url)` — this file is written as ESM source,
+ * but tsup's CJS build output has no real `import.meta.url` (esbuild
+ * leaves it `undefined` there), which would make `createRequire` throw for
+ * anyone consuming this package's `require('@kbach/react/vite')` entry.
+ * `root` works as `createRequire`'s base in either build: it's always an
+ * absolute, already-`existsSync`-validated-by-caller directory, and
+ * `require()` given `path` (itself already absolute) doesn't consult the
+ * base for resolution anyway — the base only matters for a RELATIVE
+ * specifier, which this never passes it.
+ */
+declare function loadConfigFile(root: string): KbachConfig | undefined;
+/**
+ * Resolves the theme to use, applying the same "explicit theme/config
+ * always wins over kbach.config.js auto-discovery" precedence both
+ * vite-plugin and postcss-plugin need identically.
+ */
+declare function resolveEffectiveTheme(root: string, options: {
+    theme?: ThemeConfig;
+    config?: KbachConfig;
+}): ThemeConfig;
 /**
  * Build-time static CSS generation for Vite — scans source files for
  * Kbach class strings, resolves them through the same Rust engine the
@@ -36,7 +66,13 @@ interface KbachPluginOptions {
  * `src/kbach.css` to exist at a fixed conventional path (create it with
  * `/* kbach:start *\/` / `/* kbach:end *\/` markers) rather than scanning
  * the whole project for a file named kbach.css.
+ *
+ * The actual scanning/resolution/generation logic lives in
+ * `staticCss/engine.ts`, shared with `postcss-plugin/index.ts` (Next.js/
+ * webpack/Turbopack) — this file is now just the Vite-specific wiring:
+ * plugin lifecycle hooks, the dev-server watcher, and the debounced
+ * file-write.
  */
 declare function kbach(options?: KbachPluginOptions): Plugin;
 
-export { type KbachPluginOptions, kbach };
+export { CSS_SYNC_DEBOUNCE_MS, DEFAULT_SCAN_DIRS, type KbachPluginOptions, kbach, loadConfigFile, resolveEffectiveTheme };

package/dist/vite-plugin.d.ts

@@ -28,6 +28,36 @@ interface KbachPluginOptions {
      */
     safelist?: string[];
 }
+declare const DEFAULT_SCAN_DIRS: string[];
+declare const CSS_SYNC_DEBOUNCE_MS = 50;
+/**
+ * Auto-discovers `kbach.config.js` at the project root — `undefined` if it
+ * doesn't exist (the common case: most projects have no customization at
+ * all, so this is a silent, expected no-op, not a warning).
+ *
+ * Uses `require()` (a real project's `kbach.config.js` is plain CommonJS,
+ * `module.exports = {...}`, matching every example in this package's own
+ * README), built via `createRequire(root)` rather than
+ * `createRequire(import.meta.url)` — this file is written as ESM source,
+ * but tsup's CJS build output has no real `import.meta.url` (esbuild
+ * leaves it `undefined` there), which would make `createRequire` throw for
+ * anyone consuming this package's `require('@kbach/react/vite')` entry.
+ * `root` works as `createRequire`'s base in either build: it's always an
+ * absolute, already-`existsSync`-validated-by-caller directory, and
+ * `require()` given `path` (itself already absolute) doesn't consult the
+ * base for resolution anyway — the base only matters for a RELATIVE
+ * specifier, which this never passes it.
+ */
+declare function loadConfigFile(root: string): KbachConfig | undefined;
+/**
+ * Resolves the theme to use, applying the same "explicit theme/config
+ * always wins over kbach.config.js auto-discovery" precedence both
+ * vite-plugin and postcss-plugin need identically.
+ */
+declare function resolveEffectiveTheme(root: string, options: {
+    theme?: ThemeConfig;
+    config?: KbachConfig;
+}): ThemeConfig;
 /**
  * Build-time static CSS generation for Vite — scans source files for
  * Kbach class strings, resolves them through the same Rust engine the
@@ -36,7 +66,13 @@ interface KbachPluginOptions {
  * `src/kbach.css` to exist at a fixed conventional path (create it with
  * `/* kbach:start *\/` / `/* kbach:end *\/` markers) rather than scanning
  * the whole project for a file named kbach.css.
+ *
+ * The actual scanning/resolution/generation logic lives in
+ * `staticCss/engine.ts`, shared with `postcss-plugin/index.ts` (Next.js/
+ * webpack/Turbopack) — this file is now just the Vite-specific wiring:
+ * plugin lifecycle hooks, the dev-server watcher, and the debounced
+ * file-write.
  */
 declare function kbach(options?: KbachPluginOptions): Plugin;
 
-export { type KbachPluginOptions, kbach };
+export { CSS_SYNC_DEBOUNCE_MS, DEFAULT_SCAN_DIRS, type KbachPluginOptions, kbach, loadConfigFile, resolveEffectiveTheme };