@kbach/react-native 1.0.0-beta.3 → 1.0.0-beta.31

package/dist/{jsx-runtime.mjs → jsx-runtime.web.mjs}

@@ -2,8 +2,8 @@ import {
   Fragment,
   jsx,
   jsxs
-} from "./chunk-UP5ZN7CN.mjs";
-import "./chunk-7KUNKZBM.mjs";
+} from "./chunk-FLPPVP5G.mjs";
+import "./chunk-ZYE4VIZE.mjs";
 export {
   Fragment,
   jsx,

package/dist/theme.d.ts

@@ -0,0 +1,54 @@
+/**
+ * A plain hex value (static — same in both modes), or a `{ light, dark }`
+ * pair a caller sets manually in their own theme. Fully opt-in per color:
+ * nothing here picks a "dark variant" automatically. Only `useColors()`
+ * (a JS-value read, not a `className`) understands this shape — utility
+ * CLASS resolution (`bg-blue-6`) on native/Expo Go stays plain-string-only,
+ * same as it always was (dark mode for a CLASS is the separate `dark:`
+ * modifier, gated live at resolve time — see `resolve_style.rs`); a
+ * mode-aware entry referenced directly by a class name just doesn't
+ * resolve there, mirroring `resolvers/color.rs`'s own `lookup_hex`
+ * (`ColorValue::Plain` only, `ModeAware` -> `None`) exactly, same as it
+ * would on the web engine too.
+ */
+type ColorEntry = string | {
+    light: string;
+    dark: string;
+};
+/**
+ * Real Tailwind's `theme.container` config, mirroring
+ * `packages/core-engine/src/theme.rs`'s `ContainerConfig` exactly. `center`/
+ * `padding` DO reach native now (unlike the max-width breakpoint ladder,
+ * which is a `css.rs`-only concept with nothing to generate on native at
+ * all) — `resolvers::layout::resolve`'s `"container"` arm is shared by both
+ * dispatchers, and `margin`/`padding` are ordinary RN style properties.
+ */
+interface ContainerConfig {
+    center?: boolean;
+    padding?: string;
+}
+interface ThemeConfig {
+    colors: Record<string, ColorEntry>;
+    spacing: Record<string, number>;
+    screens: Record<string, number>;
+    /**
+     * e.g. "sans" -> "Inter, sans-serif". Optional, matching the Rust
+     * engine's own `#[serde(default)]`. Write it as a real web-shaped
+     * fallback stack even on this native-first package — native's own
+     * resolver strips it down to a single bare name at resolve time (RN's
+     * `fontFamily` prop can't take a fallback list — see
+     * `resolvers/mod.rs`'s `first_font_name`), so the SAME config still
+     * works unmodified on Expo Web, which needs the full stack.
+     */
+    fontFamily?: Record<string, string>;
+    darkMode: 'attribute' | 'class' | 'media';
+    /** Optional, matching `ContainerConfig`'s own `#[serde(default)]` on the Rust side. */
+    container?: ContainerConfig;
+}
+declare const defaultTheme: ThemeConfig;
+declare function setTheme(theme: ThemeConfig): void;
+declare function getTheme(): ThemeConfig;
+/** Memoized JSON serialization of the active theme — passed across the JNI boundary. */
+declare function getThemeJson(): string;
+
+export { type ColorEntry, type ContainerConfig, type ThemeConfig, defaultTheme, getTheme, getThemeJson, setTheme };

package/dist/{chunk-7KUNKZBM.mjs → theme.js}

@@ -1,3 +1,32 @@
+"use strict";
+var __defProp = Object.defineProperty;
+var __getOwnPropDesc = Object.getOwnPropertyDescriptor;
+var __getOwnPropNames = Object.getOwnPropertyNames;
+var __hasOwnProp = Object.prototype.hasOwnProperty;
+var __export = (target, all) => {
+  for (var name in all)
+    __defProp(target, name, { get: all[name], enumerable: true });
+};
+var __copyProps = (to, from, except, desc) => {
+  if (from && typeof from === "object" || typeof from === "function") {
+    for (let key of __getOwnPropNames(from))
+      if (!__hasOwnProp.call(to, key) && key !== except)
+        __defProp(to, key, { get: () => from[key], enumerable: !(desc = __getOwnPropDesc(from, key)) || desc.enumerable });
+  }
+  return to;
+};
+var __toCommonJS = (mod) => __copyProps(__defProp({}, "__esModule", { value: true }), mod);
+
+// src/theme.ts
+var theme_exports = {};
+__export(theme_exports, {
+  defaultTheme: () => defaultTheme,
+  getTheme: () => getTheme,
+  getThemeJson: () => getThemeJson,
+  setTheme: () => setTheme
+});
+module.exports = __toCommonJS(theme_exports);
+
 // src/generatedPalette.ts
 var PALETTE = {
   "amber-1": "#fffbeb",
@@ -278,16 +307,51 @@ var PALETTE = {
 // src/theme.ts
 var defaultTheme = {
   colors: PALETTE,
+  // Real Tailwind's default spacing scale in full — every step is exactly
+  // `n * 4px`, including the fractional `.5` steps (`1.5` -> 6px, `2.5` ->
+  // 10px, `3.5` -> 14px) and the "px" literal (a bare 1px). Only the
+  // "usual stops", though — `jsEngine/shared.ts`'s `spacingPx` (and the
+  // native Rust dispatcher's own `spacing_px`) falls back to Tailwind v4's
+  // live `n * 4px` formula for any bare numeric step not listed here
+  // (`p-0.25`, `w-13`, ...), so this table names the common values and
+  // gives a theme override something to target, not the full resolvable
+  // set. Mirrors @kbach/react's theme.ts exactly.
   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`/etc.
-    // Mirrors the identical fix in @kbach/react's theme.ts.
     "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,
@@ -296,7 +360,20 @@ 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. On native these three still effectively no-op (see
+  // `first_font_name`'s own doc comment for why a generic CSS keyword
+  // isn't a real loadable font) — only a caller-configured custom name
+  // changes native rendering; Expo Web uses the full stack as-is.
+  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'
+  },
+  darkMode: "attribute",
+  // Empty by default, matching real Tailwind's own defaults.
+  container: {}
 };
 var activeTheme = defaultTheme;
 var activeThemeJson = JSON.stringify(defaultTheme);
@@ -310,72 +387,10 @@ function getTheme() {
 function getThemeJson() {
   return activeThemeJson;
 }
-
-// src/darkModeStore.ts
-import { Appearance } from "react-native";
-var listeners = /* @__PURE__ */ new Set();
-function systemPrefersDark() {
-  return Appearance.getColorScheme() === "dark";
-}
-function resolveIsDark(m) {
-  return m === "system" ? systemPrefersDark() : m === "dark";
-}
-var mode = "system";
-var isDark = resolveIsDark(mode);
-var hasExplicitChoice = false;
-var subscription = Appearance.addChangeListener(({ colorScheme }) => {
-  if (mode !== "system") return;
-  isDark = colorScheme === "dark";
-  notify();
-});
-function notify() {
-  for (const listener of listeners) listener();
-}
-function getGlobalDarkMode() {
-  return isDark;
-}
-function getGlobalThemeMode() {
-  return mode;
-}
-function setGlobalThemeMode(nextMode) {
-  mode = nextMode;
-  isDark = resolveIsDark(nextMode);
-  hasExplicitChoice = true;
-  notify();
-}
-function toggleGlobalDarkMode() {
-  setGlobalThemeMode(isDark ? "light" : "dark");
-}
-function subscribeGlobalDarkMode(listener) {
-  listeners.add(listener);
-  return () => listeners.delete(listener);
-}
-function seedDefaultMode(fallback) {
-  if (hasExplicitChoice || mode === fallback) return;
-  mode = fallback;
-  isDark = resolveIsDark(fallback);
-  notify();
-}
-
-// src/nativeBridge.ts
-import { Dimensions, TurboModuleRegistry } from "react-native";
-function resolveStyle(classString, pressed = false) {
-  const KbachModule = TurboModuleRegistry.getEnforcing("KbachModule");
-  const colorScheme = getGlobalDarkMode() ? "dark" : "light";
-  const width = Dimensions.get("window").width;
-  const json = KbachModule.resolveStyle(classString, getThemeJson(), colorScheme, pressed, width);
-  return JSON.parse(json);
-}
-
-export {
+// Annotate the CommonJS export names for ESM import in node:
+0 && (module.exports = {
   defaultTheme,
-  setTheme,
   getTheme,
-  getGlobalDarkMode,
-  getGlobalThemeMode,
-  setGlobalThemeMode,
-  toggleGlobalDarkMode,
-  subscribeGlobalDarkMode,
-  seedDefaultMode,
-  resolveStyle
-};
+  getThemeJson,
+  setTheme
+});

package/package.json

@@ -1,8 +1,18 @@
 {
   "name": "@kbach/react-native",
-  "version": "1.0.0-beta.3",
-  "description": "Kbach's utility-class styling engine for React Native — the same class names as @kbach/react, resolved to a StyleSheet-ready style object via a Kotlin/JNI TurboModule. Ships its own native Android module (Kotlin + prebuilt Rust/JNI .so) — one npm install, no separate native package. Beta, Android-only. Works with the React Native CLI or an Expo dev client (not Expo Go).",
-  "keywords": ["css", "react-native", "expo", "tailwind", "utility-first", "styling", "android"],
+  "version": "1.0.0-beta.31",
+  "description": "Kbach's utility-class styling engine for React Native — the same class names as @kbach/react, resolved to a StyleSheet-ready style object via a Kotlin/JNI TurboModule (native), the same WASM engine @kbach/react uses (Expo Web / react-native-web), or a pure-JS fallback engine (Expo Go). Ships its own native Android module — one npm install, no separate native package. Beta. Native is Android-only (no iOS bridge yet); works with the React Native CLI, an Expo dev client, AND Expo Go (a reduced-coverage pure-JS fallback, since Expo Go can't load any custom native module).",
+  "keywords": [
+    "css",
+    "react-native",
+    "expo",
+    "tailwind",
+    "utility-first",
+    "styling",
+    "android",
+    "web",
+    "wasm"
+  ],
   "license": "MIT",
   "author": "semsakadanupol",
   "repository": {
@@ -17,42 +27,77 @@
   "publishConfig": {
     "access": "public"
   },
-  "files": ["dist", "src/babel-plugin.js", "android/build.gradle", "android/src", "specs", "react-native.config.js"],
+  "files": [
+    "dist",
+    "src/babel-plugin.js",
+    "android/build.gradle",
+    "android/src",
+    "specs",
+    "react-native.config.js"
+  ],
   "source": "./src/index.ts",
   "main": "./dist/index.js",
-  "module": "./dist/index.mjs",
   "types": "./dist/index.d.ts",
   "exports": {
     ".": {
       "types": "./dist/index.d.ts",
       "source": "./src/index.ts",
-      "import": "./dist/index.mjs",
+      "browser": {
+        "import": "./dist/index.web.mjs",
+        "require": "./dist/index.web.js"
+      },
+      "node": {
+        "import": "./dist/index.web.mjs",
+        "require": "./dist/index.web.js"
+      },
+      "react-native": "./dist/index.js",
       "require": "./dist/index.js"
     },
     "./jsx-runtime": {
       "types": "./dist/jsx-runtime.d.ts",
       "source": "./src/jsx-runtime.tsx",
-      "import": "./dist/jsx-runtime.mjs",
+      "browser": {
+        "import": "./dist/jsx-runtime.web.mjs",
+        "require": "./dist/jsx-runtime.web.js"
+      },
+      "node": {
+        "import": "./dist/jsx-runtime.web.mjs",
+        "require": "./dist/jsx-runtime.web.js"
+      },
+      "react-native": "./dist/jsx-runtime.js",
       "require": "./dist/jsx-runtime.js"
     },
     "./jsx-dev-runtime": {
       "types": "./dist/jsx-dev-runtime.d.ts",
       "source": "./src/jsx-dev-runtime.tsx",
-      "import": "./dist/jsx-dev-runtime.mjs",
+      "browser": {
+        "import": "./dist/jsx-dev-runtime.web.mjs",
+        "require": "./dist/jsx-dev-runtime.web.js"
+      },
+      "node": {
+        "import": "./dist/jsx-dev-runtime.web.mjs",
+        "require": "./dist/jsx-dev-runtime.web.js"
+      },
+      "react-native": "./dist/jsx-dev-runtime.js",
       "require": "./dist/jsx-dev-runtime.js"
     },
     "./babel-plugin": "./src/babel-plugin.js"
   },
   "scripts": {
-    "build": "tsup",
-    "dev": "tsup --watch",
+    "build": "node -e \"require('fs').rmSync('dist',{recursive:true,force:true})\" && tsup",
+    "dev": "node -e \"require('fs').rmSync('dist',{recursive:true,force:true})\" && tsup --watch",
     "test": "vitest run --passWithNoTests",
+    "test:coverage": "vitest run --coverage --passWithNoTests",
     "lint": "tsc --noEmit",
-    "generate:colors": "node ../core-engine/scripts/generate-palette.mjs src/generatedPalette.ts"
+    "generate:colors": "node ../core-engine/scripts/generate-palette.mjs src/generatedPalette.ts",
+    "generate:wasm-base64": "node ../core-engine/scripts/generate-wasm-base64.mjs src/wasmBinary.generated.ts",
+    "generate:web-glue": "node ../core-engine/scripts/generate-web-glue.mjs src/wasmGlue.generated.ts"
   },
   "devDependencies": {
     "@types/react": "^19.2.0",
     "@types/react-test-renderer": "^19.1.0",
+    "@vitest/coverage-v8": "^1.6.1",
+    "jsdom": "^30.0.1",
     "react-native": "^0.87.0",
     "react-test-renderer": "^19.2.0",
     "tsup": "^8.0.0",

package/src/babel-plugin.js

@@ -1,5 +1,9 @@
 'use strict';
 
+const path = require('path');
+const fs = require('fs');
+const template = require('@babel/template').default;
+
 /**
  * Injects a per-file `@jsxImportSource @kbach/react-native` pragma comment
  * so Metro's JSX transform routes className resolution through
@@ -19,9 +23,67 @@
  * Deliberately NOT porting old-kbach's build-time class-resolution half
  * (the __kbachStyles fast path) — resolution happens at the (already
  * synchronous) native-bridge call inside the jsx-runtime instead (see
- * nativeBridge.ts), so this plugin's only job is the pragma injection.
+ * nativeBridge.ts), so this plugin's only job is the pragma injection —
+ * PLUS one more, added later: auto-applying `kbach.config.js` if one
+ * exists (see `getConfigStatement`'s own doc comment), so a project never
+ * needs its own explicit `applyKbachConfig(kbachConfig)` call at all. That
+ * addition deliberately still stops short of old-kbach's own version of
+ * this (an mtime-polling live-reload of the config, re-checked on every
+ * file) — a Babel-plugin-level change needs a dev-server restart to take
+ * effect either way, so a one-time check per (root, process) pair is
+ * enough, and much simpler to reason about.
+ */
+
+// Keyed by the root directory checked — undefined = not checked yet for
+// that root, null = checked, no kbach.config.js found there. A Babel/Metro
+// worker process transforms many files over its lifetime — this makes the
+// existsSync + template-build work happen ONCE per root, not on every
+// single file `pre()` runs for.
+const _configStatementCache = new Map();
+
+/**
+ * Builds the (uncompiled) AST statement that applies `kbach.config.js`,
+ * cached per `root` after the first call — `null` if no such file exists
+ * there. `root` defaults to `process.cwd()` (how `metro start`/`expo
+ * start` are conventionally invoked) at the plugin's own call site below;
+ * pass `{ configRoot: '...' }` as this plugin's Babel options if your
+ * `kbach.config.js` lives somewhere else (a monorepo where Metro's actual
+ * working directory isn't the app's own root, for instance).
+ *
+ * The injected statement is a plain `require(...).applyKbachConfig(require(...))`
+ * — no try/catch around it. `kbach.config.js`'s own path is only ever
+ * baked in here after `existsSync` already confirmed it exists, so the
+ * only way this could still throw is a genuine bug in that file (a syntax
+ * error, a bad nested require) — letting that surface as a real, visible
+ * Metro bundling error is far better than silently swallowing it: a
+ * developer's real customization would otherwise go missing with zero
+ * indication why, exactly the kind of headache a good default should avoid.
+ *
+ * `@babel/template` builds this from a plain string with the absolute path
+ * JSON-escaped directly into it (correct on Windows too, backslashes and
+ * all) — simpler than building the equivalent `@babel/types` node graph by
+ * hand for one straightforward statement.
  */
-module.exports = function kbachReactNativeBabelPlugin() {
+function getConfigStatement(root) {
+  if (_configStatementCache.has(root)) return _configStatementCache.get(root);
+
+  const configPath = path.join(root, 'kbach.config.js');
+  if (!fs.existsSync(configPath)) {
+    _configStatementCache.set(root, null);
+    return null;
+  }
+
+  const buildStatement = template(
+    `require('@kbach/react-native').applyKbachConfig(require(${JSON.stringify(configPath)}));`,
+  );
+  const statement = buildStatement();
+  _configStatementCache.set(root, statement);
+  return statement;
+}
+
+module.exports = function kbachReactNativeBabelPlugin(_babel, options) {
+  const configRoot = (options && options.configRoot) || process.cwd();
+
   return {
     name: 'kbach-react-native',
     pre(file) {
@@ -33,7 +95,17 @@ module.exports = function kbachReactNativeBabelPlugin() {
       if (!alreadySet) {
         comments.unshift({ type: 'CommentLine', value: ' @jsxImportSource @kbach/react-native' });
       }
+
+      const configStatement = getConfigStatement(configRoot);
+      if (configStatement) {
+        file.ast.program.body.unshift(configStatement);
+      }
     },
     visitor: {},
   };
 };
+
+/** Exported for tests only — clears the per-root config-file cache between test cases. */
+module.exports._resetForTests = function resetForTests() {
+  _configStatementCache.clear();
+};

package/dist/chunk-UP5ZN7CN.mjs

@@ -1,44 +0,0 @@
-import {
-  resolveStyle
-} from "./chunk-7KUNKZBM.mjs";
-
-// src/jsx-runtime.tsx
-import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
-import { Fragment } from "react";
-import { Pressable } from "react-native";
-function makeElement(isStaticChildren, type, props, key) {
-  return (isStaticChildren ? _jsxs : _jsx)(type, props, key);
-}
-function resolvedStyleFor(classStrRaw, userStyle, pressed) {
-  const resolved = resolveStyle(classStrRaw, pressed);
-  if (userStyle === void 0) {
-    return resolved;
-  }
-  if (typeof userStyle === "function") {
-    return [resolved, userStyle({ pressed })];
-  }
-  return [resolved, userStyle];
-}
-function processElement(type, rawProps, key, isStaticChildren) {
-  if (type === null || typeof type === "symbol" || !rawProps) {
-    return makeElement(isStaticChildren, type, rawProps ?? {}, key);
-  }
-  const { className: classStrRaw, style: userStyle, ...rest } = rawProps;
-  if (typeof classStrRaw !== "string") {
-    return makeElement(isStaticChildren, type, rawProps, key);
-  }
-  const finalStyle = type === Pressable ? (state) => resolvedStyleFor(classStrRaw, userStyle, state.pressed) : resolvedStyleFor(classStrRaw, userStyle, false);
-  return makeElement(isStaticChildren, type, { ...rest, style: finalStyle }, key);
-}
-function jsx(type, props, key) {
-  return processElement(type, props, key, false);
-}
-function jsxs(type, props, key) {
-  return processElement(type, props, key, true);
-}
-
-export {
-  Fragment,
-  jsx,
-  jsxs
-};

package/dist/index.d.mts

@@ -1,161 +0,0 @@
-import * as react from 'react';
-import { ReactNode } from 'react';
-
-interface ThemeConfig {
-    /** Plain hex only, this pass — e.g. "blue-6" -> "#2563eb" */
-    colors: Record<string, string>;
-    spacing: Record<string, number>;
-    screens: Record<string, number>;
-    darkMode: 'attribute' | 'class' | 'media';
-}
-declare const defaultTheme: ThemeConfig;
-declare function setTheme(theme: ThemeConfig): void;
-declare function getTheme(): ThemeConfig;
-
-interface StyleObject {
-    [key: string]: string | number;
-}
-/**
- * Calls the Rust engine via the KbachModule TurboModule (see
- * apps/native-sandbox/android/.../KbachModule.kt and
- * packages/core-engine/src/resolve_style.rs) and returns a plain style
- * object ready for RN's `style` prop. Synchronous — no async init step,
- * unlike the web/WASM path, since JSI-backed TurboModule methods are
- * available as soon as the module is loaded.
- *
- * Reads `getGlobalDarkMode()` (darkModeStore.ts) fresh on every call (no
- * caching) so `dark:` resolves correctly whenever this runs. That store —
- * not a direct `Appearance.getColorScheme()` read, which this function
- * used prior to `<ThemeProvider>` support — is what makes an explicit
- * `setGlobalThemeMode('dark')`/`toggle()` override actually affect
- * rendering; the store itself falls back to tracking `Appearance` live
- * whenever the mode is `'system'` (its own default), so nothing regresses
- * for apps that never touch the override API at all. This function itself
- * has no subscription of its own, so nothing re-renders just because the
- * store's value changed — call `useGlobalDarkMode()` (or consume
- * `useTheme()`'s `isDark`) somewhere in the tree for that, NOT React
- * Native's own `useColorScheme()`, which only reflects the raw OS setting
- * and would miss an explicit override entirely.
- *
- * Phase 11 originally shipped with live in-place theme switching unverified
- * (a `uiMode` toggle triggered a re-render but `Appearance.getColorScheme()`
- * kept returning a stale value). Root-caused in Phase 12 while debugging an
- * unrelated `active:` failure: `apps/native-sandbox` has its own separate
- * `node_modules/react-native` (excluded from the npm workspace since Phase
- * 5), while `packages/react-native` resolved `react-native` hierarchically
- * up to a *different* copy at the repo root — two physical module
- * instances, so a `useColorScheme()` subscription and an
- * `Appearance.getColorScheme()` read were silently talking to two separate
- * copies of the Appearance module. Fixed by forcing a single instance via
- * `resolver.resolveRequest` in apps/native-sandbox/metro.config.js; live
- * theme switching (and `active:`, the bug that surfaced this) both verified
- * working after the fix — see Phase 12. Still relevant here: darkModeStore.ts
- * itself calls `Appearance.addChangeListener`, so the same dual-instance
- * failure mode would silently break the 'system' fallback path too if that
- * metro.config.js fix ever regressed.
- *
- * `pressed` gates the `active:` modifier — unlike `colorScheme`, there's no
- * system-level getter for "is this element currently pressed"; only RN's
- * `Pressable` ever knows this, so it's passed in directly by the caller
- * (jsx-runtime, from Pressable's own style-function callback) rather than
- * queried here. Defaults to `false` for every other element type.
- *
- * `width` gates `sm:`/`md:`/`lg:`/`xl:`/`2xl:` against the active theme's
- * `screens` scale (resolve_style.rs's `native_modifier_state`) — read fresh
- * from `Dimensions.get('window').width` on every call, the same "no
- * caching, no store" choice `colorScheme`/`pressed` already make, and for
- * the same reason: unlike dark mode there's no explicit-override concept to
- * preserve here (nobody manually overrides their screen width), so a plain
- * synchronous read is enough — no need for the subscribable store
- * darkModeStore.ts is for. As with `colorScheme`, this function has no
- * subscription of its own, so rotating/resizing the window doesn't
- * re-render anything by itself — call RN's own `useWindowDimensions()`
- * somewhere in the tree for that (same role `useColorScheme()` plays for
- * `dark:` in apps/native-sandbox/App.tsx).
- */
-declare function resolveStyle(classString: string, pressed?: boolean): StyleObject;
-
-/**
- * Native port of @kbach/react's darkModeStore.ts — same architecture (a
- * single module-level store is the real source of truth;
- * ThemeProvider/useTheme are a thin, OPTIONAL wrapper around it; every
- * function here works standalone with no provider mounted anywhere), with
- * two real platform differences from the web version:
- *
- * 1. No persistence. There's no React-Native-builtin equivalent of
- *    localStorage — adding one would mean forcing a real native dependency
- *    (e.g. @react-native-async-storage/async-storage) on every consumer,
- *    even ones that don't want it. The mode always starts at 'system' on a
- *    fresh app launch. If you want persistence, read your own storage at
- *    startup (before your first render) and call setGlobalThemeMode() with
- *    the result — same "seed once, no built-in write-back" shape as
- *    seedDefaultMode() below, just driven by your own storage instead of
- *    one this package picks for you.
- * 2. No DOM to "apply" the resolved mode to. On web, applyToDom() flips a
- *    class/attribute the generated CSS's `dark:` selectors match against.
- *    On native there's no CSS at all — nativeBridge.ts's resolveStyle()
- *    reads getGlobalDarkMode() directly on every call instead of querying
- *    Appearance.getColorScheme() itself, which is what actually makes an
- *    explicit override affect rendering (previously that function always
- *    read the raw OS setting, so it had no way to reflect a user choice —
- *    see nativeBridge.ts's own comment on this for why that's the one
- *    genuinely fixed bug this change introduces, not just a new feature).
- */
-type ThemeMode = 'light' | 'dark' | 'system';
-declare function getGlobalDarkMode(): boolean;
-declare function getGlobalThemeMode(): ThemeMode;
-/** Explicit user choice — takes priority over any later `<ThemeProvider defaultMode>` seed (see `seedDefaultMode` below). Not persisted; see this module's own doc comment. */
-declare function setGlobalThemeMode(nextMode: ThemeMode): void;
-declare function toggleGlobalDarkMode(): void;
-declare function subscribeGlobalDarkMode(listener: () => void): () => void;
-
-/**
- * Reactive read of the global dark-mode store — works with or without a
- * `<ThemeProvider>` mounted anywhere in the tree, since it subscribes to
- * `darkModeStore.ts` directly. No server-snapshot argument (unlike
- * @kbach/react's web version) — React Native has no SSR concept at all,
- * so there's no third argument for `useSyncExternalStore` to need.
- */
-declare function useGlobalDarkMode(): boolean;
-
-interface ThemeProviderProps {
-    children: ReactNode;
-    /**
-     * Applied once, on this provider's first mount, but ONLY if nothing has
-     * made an explicit mode choice yet (see
-     * `darkModeStore.ts::seedDefaultMode`) — an explicit prior choice always
-     * wins over a component's own default. Unlike @kbach/react's web
-     * version, there's no persisted value to check here — see
-     * darkModeStore.ts's own doc comment on why this package doesn't persist
-     * the mode across app launches.
-     */
-    defaultMode?: ThemeMode;
-}
-/**
- * Native port of @kbach/react's `ThemeProvider` — a thin, OPTIONAL React
- * Context wrapper around `darkModeStore.ts`'s single global store, not the
- * source of truth itself. Because the store is global, MULTIPLE mounted
- * providers share the exact same `mode`/`isDark` state rather than each
- * getting their own scoped value — mounting more than one is very likely a
- * mistake (each fighting over the same state via a different
- * `defaultMode`), so this warns once in dev, matching the web version's
- * identical guard.
- */
-declare function ThemeProvider({ children, defaultMode }: ThemeProviderProps): react.JSX.Element;
-
-interface ThemeContextValue {
-    mode: ThemeMode;
-    isDark: boolean;
-    setMode: (mode: ThemeMode) => void;
-    toggle: () => void;
-}
-/**
- * Requires a `<ThemeProvider>` ancestor — throws otherwise, since a
- * component that destructures `{ mode, setMode }` genuinely needs Context
- * (unlike a component that just wants the dark/light boolean, which should
- * reach for `useGlobalDarkMode()` instead and never needs a provider at
- * all).
- */
-declare function useTheme(): ThemeContextValue;
-
-export { type StyleObject, type ThemeConfig, type ThemeContextValue, type ThemeMode, ThemeProvider, type ThemeProviderProps, defaultTheme, getGlobalDarkMode, getGlobalThemeMode, getTheme, resolveStyle, setGlobalThemeMode, setTheme, subscribeGlobalDarkMode, toggleGlobalDarkMode, useGlobalDarkMode, useTheme };