@kbach/react-native 1.0.0-beta.50 → 1.0.0-beta.52

package/dist/jsx-runtime.web.mjs

@@ -2,8 +2,8 @@ import {
   Fragment,
   jsx,
   jsxs
-} from "./chunk-SC3L5I7H.mjs";
-import "./chunk-3KLOVONL.mjs";
+} from "./chunk-HVGMZKV7.mjs";
+import "./chunk-Z5Q3FGXR.mjs";
 export {
   Fragment,
   jsx,

package/dist/theme.d.ts

@@ -46,6 +46,31 @@ interface ThemeConfig {
     container?: ContainerConfig;
 }
 declare const defaultTheme: ThemeConfig;
+/**
+ * Idempotent by CONTENT, not just a plain assignment — deliberately, not a
+ * micro-optimization. The babel plugin (`babel-plugin.js`) injects
+ * `applyKbachConfig(require('kbach.config.js'))` at the top of EVERY user
+ * file, not just one entry point, so it re-runs on every single file
+ * Metro (re-)executes. Editing `kbach.config.js` itself under Expo Fast
+ * Refresh forces Metro to invalidate and re-execute every file that
+ * requires it — which, because of that injection, is the entire app, not
+ * just the file you're looking at. A plain unconditional reassignment here
+ * would hand every one of those re-executions a BRAND NEW theme object
+ * (`resolveKbachConfig` always builds one fresh) even when the config's
+ * actual content hasn't changed, which in turn invalidates every
+ * `useColors()` call's `useMemo` (keyed on this object's identity) and
+ * re-evaluates `usesModeAwareColor()` for every reactive element
+ * (jsxRuntimeCore.ts) across the whole tree, all at once, right as Fast
+ * Refresh is already mid-teardown/rebuild for that same app-wide
+ * invalidation — reported live as "Unable to find node on an unmounted
+ * component," a known-flaky class of React Native Fast Refresh race that
+ * this amount of simultaneous churn measurably worsens. Comparing against
+ * the JSON serialization this function already computes (previously only
+ * for the JNI boundary, see `getThemeJson`) costs nothing new — it's the
+ * same computation the old code did unconditionally — it just skips the
+ * assignment (and therefore the reference change every downstream
+ * consumer sees) when the content is unchanged.
+ */
 declare function setTheme(theme: ThemeConfig): void;
 declare function getTheme(): ThemeConfig;
 /** Memoized JSON serialization of the active theme — passed across the JNI boundary. */

package/dist/theme.js

@@ -378,8 +378,10 @@ var defaultTheme = {
 var activeTheme = defaultTheme;
 var activeThemeJson = JSON.stringify(defaultTheme);
 function setTheme(theme) {
+  const json = JSON.stringify(theme);
+  if (json === activeThemeJson) return;
   activeTheme = theme;
-  activeThemeJson = JSON.stringify(theme);
+  activeThemeJson = json;
 }
 function getTheme() {
   return activeTheme;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kbach/react-native",
-  "version": "1.0.0-beta.50",
+  "version": "1.0.0-beta.52",
   "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",