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

package/dist/jsx-runtime.web.mjs

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

package/dist/{clsx-BLLSnqAa.d.ts → semanticElements-Bk3TB-vt.d.ts}

@@ -1,7 +1,8 @@
 import { ThemeConfig, ContainerConfig } from './theme';
 import { ThemeMode } from './darkModeStore';
-import * as react from 'react';
+import * as React from 'react';
 import { ReactNode } from 'react';
+import { PressableProps, TextProps } from 'react-native';
 
 /**
  * A `kbach.config.js`-style theme customization — same shape as
@@ -165,7 +166,7 @@ interface ThemeProviderProps {
  * state — mounting more than one is very likely a mistake, so this warns
  * once in dev.
  */
-declare function ThemeProvider({ children, defaultMode, persist }: ThemeProviderProps): react.JSX.Element;
+declare function ThemeProvider({ children, defaultMode, persist }: ThemeProviderProps): React.JSX.Element;
 
 interface ColorScale {
     /** `colors.blue[6]` -> raw value */
@@ -274,4 +275,60 @@ type ClassArray = ClassValue[];
  */
 declare function clsx(...inputs: ClassValue[]): string;
 
-export { type ClassArray as C, type KbachConfig as K, ThemeProvider as T, type ClassDictionary as a, type ClassValue as b, type ColorScale as c, type ColorsAPI as d, type ThemeProviderProps as e, type ThemeState as f, type ThemeStorageAdapter as g, applyKbachConfig as h, clsx as i, useDynamicToken as j, useTheme as k, resolveKbachConfig as r, useColors as u };
+/**
+ * On Expo Web, `react-native-web` renders a bare `<View>`/`<Text>` as a
+ * plain `<div>`/`<span>` by default — confirmed directly in its own
+ * source (`exports/View/index.js`, `exports/Text/index.js`). That's
+ * NOTHING to do with Kbach: this package's jsx-runtime never reads or
+ * substitutes the JSX element type at all (`processElement` in
+ * `jsxRuntimeCore(.web).ts` only ever destructures `className`/`style`,
+ * passing `type` straight through unchanged) — whatever tag shows up is
+ * exactly whatever component the app wrote.
+ *
+ * `react-native-web` already has a real fix for this that nothing here
+ * needs to add: an `accessibilityRole`/`role` prop on ANY host component
+ * makes it render the matching real HTML element instead
+ * (`propsToAccessibilityComponent`, react-native-web's own
+ * AccessibilityUtil) — `button` -> `<button>`, `header` (+ `aria-level`,
+ * web-only) -> `<h1>`-`<h6>`, `paragraph` -> `<p>`, and so on. These
+ * components are JUST that prop, pre-set on the right underlying
+ * component — nothing Kbach-specific, and writing
+ * `<Pressable accessibilityRole="button">` directly instead of `<Button>`
+ * behaves identically. `className` keeps working on every one of these
+ * exactly like it does on a bare `Pressable`/`Text`.
+ *
+ * Deliberately NOT a `Div` or an `Input`: a plain `<View>` already IS the
+ * right generic container (there's no more-semantic alternative to ask
+ * for), and `<TextInput>` already renders a real `<input>` (or
+ * `<textarea>` when `multiline`) by default — react-native-web's own
+ * TextInput component picks that unconditionally, with no role needed at
+ * all. Only the cases that actually need a role to stop defaulting to
+ * `<div>`/`<span>` are here.
+ */
+type ButtonProps = PressableProps;
+/**
+ * A real `<button>` on Expo Web, a real accessible button on native —
+ * `<Pressable accessibilityRole="button">`, nothing else changed. Not the
+ * same thing as React Native's OWN built-in `Button` (a fixed-chrome,
+ * barely-styleable native control) — this is a styleable `Pressable`,
+ * matching how every other interactive element in a Kbach app is built.
+ */
+declare const Button: React.ForwardRefExoticComponent<PressableProps & React.RefAttributes<any>>;
+type ParagraphProps = TextProps;
+/** A real `<p>` on Expo Web — `<Text role="paragraph">`, nothing else changed. */
+declare const Paragraph: React.ForwardRefExoticComponent<TextProps & React.RefAttributes<any>>;
+type HeadingProps = TextProps;
+/** A real `<h1>` on Expo Web — `<Text accessibilityRole="header">` + the web-only level hint, nothing else changed. */
+declare const H1: React.ForwardRefExoticComponent<TextProps & React.RefAttributes<any>>;
+/** A real `<h2>` on Expo Web — see `H1`'s own doc comment. */
+declare const H2: React.ForwardRefExoticComponent<TextProps & React.RefAttributes<any>>;
+/** A real `<h3>` on Expo Web — see `H1`'s own doc comment. */
+declare const H3: React.ForwardRefExoticComponent<TextProps & React.RefAttributes<any>>;
+/** A real `<h4>` on Expo Web — see `H1`'s own doc comment. */
+declare const H4: React.ForwardRefExoticComponent<TextProps & React.RefAttributes<any>>;
+/** A real `<h5>` on Expo Web — see `H1`'s own doc comment. */
+declare const H5: React.ForwardRefExoticComponent<TextProps & React.RefAttributes<any>>;
+/** A real `<h6>` on Expo Web — see `H1`'s own doc comment. */
+declare const H6: React.ForwardRefExoticComponent<TextProps & React.RefAttributes<any>>;
+
+export { Button as B, type ClassArray as C, H1 as H, type KbachConfig as K, Paragraph as P, ThemeProvider as T, type ButtonProps as a, type ClassDictionary as b, type ClassValue as c, type ColorScale as d, type ColorsAPI as e, H2 as f, H3 as g, H4 as h, H5 as i, H6 as j, type HeadingProps as k, type ParagraphProps as l, type ThemeProviderProps as m, type ThemeState as n, type ThemeStorageAdapter as o, applyKbachConfig as p, clsx as q, resolveKbachConfig as r, useDynamicToken as s, useTheme as t, useColors as u };

package/dist/theme.js

@@ -375,19 +375,28 @@ var defaultTheme = {
   // Empty by default, matching real Tailwind's own defaults.
   container: {}
 };
-var activeTheme = defaultTheme;
-var activeThemeJson = JSON.stringify(defaultTheme);
+var GLOBAL_STATE_KEY = "__kbachReactNativeThemeState__";
+function getThemeState() {
+  const g = globalThis;
+  let state = g[GLOBAL_STATE_KEY];
+  if (!state) {
+    state = { theme: defaultTheme, json: JSON.stringify(defaultTheme) };
+    g[GLOBAL_STATE_KEY] = state;
+  }
+  return state;
+}
 function setTheme(theme) {
   const json = JSON.stringify(theme);
-  if (json === activeThemeJson) return;
-  activeTheme = theme;
-  activeThemeJson = json;
+  const state = getThemeState();
+  if (json === state.json) return;
+  state.theme = theme;
+  state.json = json;
 }
 function getTheme() {
-  return activeTheme;
+  return getThemeState().theme;
 }
 function getThemeJson() {
-  return activeThemeJson;
+  return getThemeState().json;
 }
 // Annotate the CommonJS export names for ESM import in node:
 0 && (module.exports = {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kbach/react-native",
-  "version": "1.0.0-beta.52",
+  "version": "1.0.0-beta.54",
   "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",
@@ -34,7 +34,8 @@
     "android/src",
     "specs",
     "react-native.config.js",
-    "AGENTS.md"
+    "AGENTS.md",
+    "THIRD_PARTY_NOTICES.md"
   ],
   "source": "./src/index.ts",
   "main": "./dist/index.js",