@symbiote-native/react 0.3.0 → 0.4.0

package/build/modules/animated/index.js

@@ -14,7 +14,7 @@ import { AnimatedMock } from '@symbiote-native/engine';
 export { createAnimatedComponent } from './create-animated-component.js';
 // The pure graph leaves now live in @symbiote-native/engine (they extend AnimatedWithChildren,
 // no React); re-exported here so @symbiote-native/react's Animated surface is unchanged.
-export { AnimatedProps, AnimatedStyle, AnimatedTransform } from '@symbiote-native/engine';
+export { AnimatedProps, AnimatedStyle, AnimatedTransform, } from '@symbiote-native/engine';
 // View/Text/Image are pure host primitives, so wrap them eagerly.
 const AnimatedView = createAnimatedComponent(View);
 const AnimatedText = createAnimatedComponent(Text);

package/build/modules/status-bar/index.ios.js

@@ -10,7 +10,7 @@
 // it, which is also what a bare '@symbiote-native/engine' import resolves to under vitest — so
 // this file's own engine import is already vitest-correct, no platform-selection subtlety here.
 import { useEffect } from 'react';
-import { applyStatusBarProps, statusBarImperative } from '@symbiote-native/engine';
+import { applyStatusBarProps, statusBarImperative, } from '@symbiote-native/engine';
 // StatusBar renders null and applies its props to the native module in an effect,
 // on mount and on every prop change. Simplification vs RN: RN maintains a
 // prop-merge stack so nested StatusBars compose (deepest/last wins). This module

package/build/render.js

@@ -11,10 +11,20 @@ function errorReporter(origin) {
     };
 }
 const onUncaughtError = errorReporter('react render (no error boundary)');
-// A boundary handled it, and it is still reported - the boundary decides what the USER sees, not
-// whether the developer hears about it. Upstream's nativeOnCaughtError calls the same
-// showErrorDialog as the uncaught path.
-const onCaughtError = errorReporter('react render (caught by error boundary)');
+// A boundary handled it, so it does NOT reach the native redbox — it goes to , off unless
+// DEBUG is set.
+//
+// This deliberately DIVERGES from upstream, whose nativeOnCaughtError calls the same
+// showErrorDialog as the uncaught path. The argument for upstream's choice is that the boundary
+// decides what the USER sees, not whether the developer hears. The argument against, and the one
+// this project takes: writing an ErrorBoundary IS the developer saying "I know this can throw and
+// I am handling it here". Answering that with a full-screen redbox over the fallback the app just
+// rendered contradicts the thing the app asked for, and it is the only adapter here that did it —
+// Solid's ErrorBoundary is silent, and its canary reads as correct next to React's alarming one.
+// An UNCAUGHT error still hits the redbox; the difference is exactly whether someone claimed it.
+const onCaughtError = (error, info) => {
+    dlog(() => `react render (caught by error boundary): ${String(error)}${info.componentStack ?? ''}`);
+};
 // React recovered on its own (a concurrent render retried and succeeded), so this is not fatal -
 // but it is still a real error the app swallowed a first render over. RN keeps React's
 // defaultOnRecoverableError here, which reports it globally.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@symbiote-native/react",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "description": "SymbioteNative's React adapter — a react-reconciler host config (mutation mode) driving real native iOS/Android views through stock React Native Fabric.",
   "license": "MIT",
   "repository": {
@@ -37,8 +37,8 @@
   },
   "dependencies": {
     "react-reconciler": "^0.33.0",
-    "@symbiote-native/components": "0.4.0",
-    "@symbiote-native/css-parser": "0.3.0"
+    "@symbiote-native/components": "0.5.0",
+    "@symbiote-native/css-parser": "0.4.0"
   },
   "peerDependencies": {
     "@symbiote-native/engine": ">=0.1.7",
@@ -49,8 +49,8 @@
     "@types/react": "^19.2.0",
     "@types/react-reconciler": "^0.32.2",
     "react": "19.2.3",
-    "@symbiote-native/engine": "0.2.0",
-    "@symbiote-native/test-utils": "0.1.6"
+    "@symbiote-native/engine": "0.3.0",
+    "@symbiote-native/test-utils": "0.2.0"
   },
   "scripts": {
     "typecheck": "tsc --build",