@colixsystems/widget-sdk 0.116.0 → 0.117.0

package/README.md

@@ -70,7 +70,33 @@ See the design reference for the full architecture: [`docs/architecture/widget-m
 
 ## Status
 
-`v0.112.0` — pre-publish. The package surface (types, function names, export paths) is the v1 contract; runtime behaviour for some hooks is stubbed (each hook documents what's wired and what isn't). It is **not yet published to npm**.
+`v0.117.0` — pre-publish. The package surface (types, function names, export paths) is the v1 contract; runtime behaviour for some hooks is stubbed (each hook documents what's wired and what isn't). It is **not yet published to npm**.
+
+### What's new in 0.117.0 (contract 1.89.0)
+
+**`expo-sensors` is a vetted import — widgets can read device motion.** The allowlist held no sensor package, so a step counter, a shake control, a tilt/level, or a compass had nothing to read the hardware with. `expo-sensors` (Accelerometer, Gyroscope, Magnetometer, DeviceMotion, Barometer, Pedometer, LightSensor) is now on the list as **native-only** (`platforms: ["native"]`, category `sensors`) and pinned by the Expo export.
+
+Native-only is deliberate rather than a gap: the package's own web build derives "acceleration" from `deviceorientation` **angles**, not real motion, so a shake threshold tuned in the Player would behave differently in the exported app. Split the widget and read the browser API directly on web:
+
+```jsx
+// widget.native.jsx
+import { Accelerometer } from "expo-sensors";
+
+Accelerometer.setUpdateInterval(100);
+const sub = Accelerometer.addListener(({ x, y, z }) => setReading({ x, y, z }));
+return () => sub.remove();          // ALWAYS remove it — a live sensor drains the battery
+```
+
+```jsx
+// widget.web.jsx — window.DeviceMotionEvent exposes the same hardware
+const onMotion = (e) => setReading(e.accelerationIncludingGravity);
+window.addEventListener("devicemotion", onMotion);
+return () => window.removeEventListener("devicemotion", onMotion);
+```
+
+Start the reading from a **user gesture** on both hosts — iOS Safari also needs an explicit `DeviceMotionEvent.requestPermission()` grant, and neither host delivers readings to a listener attached on mount.
+
+**Fixed: a `expo-haptics` widget failed the native build.** `expo-haptics` has been vetted since the package expansion but was never pinned in the exported app's `package.json`, so a widget importing it rendered in the web Player and broke the Expo bundle with "Unable to resolve module expo-haptics". It is pinned now, and the pairing is no longer hand-maintained: every native-capable entry on the vetted list is checked against the export's dependency set by a contract-derived test.
 
 ### What's new in 0.116.0 (contract 1.88.0)
 

package/dist/contract.cjs

@@ -2571,6 +2571,13 @@ const VETTED_IMPORTS = [
     description:
       "Renders a QR code, drawn as SVG through the vetted react-native-svg — so one `<QRCode value={…} size={…} />` covers both platforms with no split file. Pure JS with no native module of its own: the web host resolves it and the Expo export pins it, exactly like date-fns. Its `text-encoding` polyfill is opt-in for React Native < 0.75 only; the export ships RN 0.85.3, which has a global TextEncoder, so the Metro transformer that package documents is deliberately not wired up.",
   },
+  {
+    specifier: "expo-sensors",
+    platforms: ["native"],
+    category: "sensors",
+    description:
+      "Device motion hardware on the Expo export: Accelerometer, Gyroscope, Magnetometer, DeviceMotion, Barometer, Pedometer and LightSensor, each read as an addListener subscription with setUpdateInterval — always remove the subscription on unmount, a sensor left running drains the battery. Expo SDK 56 ships 56.0.x. Native-only on purpose: the package's own web build derives acceleration from deviceorientation ANGLES rather than real motion, so a shake or tilt threshold tuned on one host would read differently on the other. Author it in widget.native.jsx and pair it with a widget.web.jsx reading window.DeviceMotionEvent (accelerationIncludingGravity / rotationRate), the browser API the same hardware exposes. Both hosts need a user gesture before readings start, and iOS Safari additionally needs an explicit DeviceMotionEvent.requestPermission() grant — so gate the reading behind a Pressable, never start it on mount.",
+  },
 ];
 
 // sc-1064: CORE React infrastructure specifiers the host RESOLVES at runtime
@@ -3500,7 +3507,15 @@ const CONTRACT = deepFreeze({
   // widget can open at SCREEN level. Everything before it was clipped by the
   // layout container the widget sits in, so a preview or dialog could not leave
   // the widget's own tile on either host.
-  version: "1.88.0",
+  // 1.89.0: additive — `expo-sensors` joins VETTED_IMPORTS as a native-only
+  // `sensors` package (Accelerometer / Gyroscope / DeviceMotion / Barometer /
+  // Pedometer / LightSensor). Widgets had no path to device motion at all: the
+  // allowlist held no sensor package, so a step counter, a tilt/shake control,
+  // a level, or a compass was unbuildable. Native-only because the package's
+  // web build reads deviceorientation angles rather than real acceleration —
+  // the web half is a widget.web.jsx over window.DeviceMotionEvent. Pinned in
+  // the compiler's export dependencies, like every other native-module member.
+  version: "1.89.0",
   sharedTranslationKeys: SHARED_TRANSLATION_KEYS,
   hooks: HOOKS,
   primitives: PRIMITIVES,

package/dist/contract.js

@@ -2571,6 +2571,13 @@ const VETTED_IMPORTS = [
     description:
       "Renders a QR code, drawn as SVG through the vetted react-native-svg — so one `<QRCode value={…} size={…} />` covers both platforms with no split file. Pure JS with no native module of its own: the web host resolves it and the Expo export pins it, exactly like date-fns. Its `text-encoding` polyfill is opt-in for React Native < 0.75 only; the export ships RN 0.85.3, which has a global TextEncoder, so the Metro transformer that package documents is deliberately not wired up.",
   },
+  {
+    specifier: "expo-sensors",
+    platforms: ["native"],
+    category: "sensors",
+    description:
+      "Device motion hardware on the Expo export: Accelerometer, Gyroscope, Magnetometer, DeviceMotion, Barometer, Pedometer and LightSensor, each read as an addListener subscription with setUpdateInterval — always remove the subscription on unmount, a sensor left running drains the battery. Expo SDK 56 ships 56.0.x. Native-only on purpose: the package's own web build derives acceleration from deviceorientation ANGLES rather than real motion, so a shake or tilt threshold tuned on one host would read differently on the other. Author it in widget.native.jsx and pair it with a widget.web.jsx reading window.DeviceMotionEvent (accelerationIncludingGravity / rotationRate), the browser API the same hardware exposes. Both hosts need a user gesture before readings start, and iOS Safari additionally needs an explicit DeviceMotionEvent.requestPermission() grant — so gate the reading behind a Pressable, never start it on mount.",
+  },
 ];
 
 // sc-1064: CORE React infrastructure specifiers the host RESOLVES at runtime
@@ -3500,7 +3507,15 @@ const CONTRACT = deepFreeze({
   // widget can open at SCREEN level. Everything before it was clipped by the
   // layout container the widget sits in, so a preview or dialog could not leave
   // the widget's own tile on either host.
-  version: "1.88.0",
+  // 1.89.0: additive — `expo-sensors` joins VETTED_IMPORTS as a native-only
+  // `sensors` package (Accelerometer / Gyroscope / DeviceMotion / Barometer /
+  // Pedometer / LightSensor). Widgets had no path to device motion at all: the
+  // allowlist held no sensor package, so a step counter, a tilt/shake control,
+  // a level, or a compass was unbuildable. Native-only because the package's
+  // web build reads deviceorientation angles rather than real acceleration —
+  // the web half is a widget.web.jsx over window.DeviceMotionEvent. Pinned in
+  // the compiler's export dependencies, like every other native-module member.
+  version: "1.89.0",
   sharedTranslationKeys: SHARED_TRANSLATION_KEYS,
   hooks: HOOKS,
   primitives: PRIMITIVES,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@colixsystems/widget-sdk",
-  "version": "0.116.0",
+  "version": "0.117.0",
   "description": "Common widget interface for AppStudio. Implements WidgetManifest, WidgetContext, property schema, and helper hooks.",
   "type": "module",
   "main": "./dist/index.js",