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

package/README.md

@@ -82,6 +82,11 @@ Architecture off, turn it on in `app.json`
 EAS Build works the same way — it runs the same `prebuild` step, so no
 extra configuration beyond the two steps above.
 
+See `apps/expo-sandbox` in the [repo](https://github.com/semsakadanupol/kbach)
+for a full working reference project covering both this section and Expo
+Web below — including the `metro.config.js` a monorepo setup like this one
+needs (a plain single-app install doesn't need it).
+
 ### Expo Web
 
 **Works — no extra setup, no separate package, no init call.** `expo start
@@ -104,8 +109,9 @@ for what's covered.
 ## What this is
 
 - A JSX runtime (`@kbach/react-native/jsx-runtime`) that intercepts
-  `className`/`kb` props on every element and calls into the native bridge
-  to resolve them to a style object, synchronously, on every render.
+  `className`/`kb` props on every element and calls into the native/WASM
+  bridge (whichever platform you're on) to resolve them to a style object,
+  synchronously, on every render.
 - A Babel plugin (`@kbach/react-native/babel-plugin`) that routes your
   app's own files (never `node_modules`) through that JSX runtime via a
   per-file `@jsxImportSource` pragma.

package/dist/{chunk-ZUE6SCTE.mjs → chunk-5WK55Z56.mjs}

@@ -1,6 +1,6 @@
 import {
   resolveStyle
-} from "./chunk-KSDFO34H.mjs";
+} from "./chunk-T3HPTH62.mjs";
 import {
   createJsxFunctions
 } from "./chunk-DLIXI5OW.mjs";