Files
zeekayandHanzo Dev 629db23fd0 event: raise the floor to ^0.3.3 (>=0.3.2 has the error envelope)
@hanzo/event <=0.3.1 shipped NO Sentry envelope code — captureError() collected
and dropped. 0.3.2 added it.

This repo already RESOLVED to 0.3.3 (the caret ranges permit it), so nothing
changes here at install time. The defect is in what the observe packages
PUBLISH: declaring ^0.3.0 lets any downstream consumer legitimately resolve to
0.3.0 or 0.3.1 and silently get a dead error plane. The floor now states the
real requirement.

pnpm install --frozen-lockfile green; @hanzo/observe 28 tests pass.

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-26 23:47:07 -07:00
..

@hanzo/observe-native

Native + desktop binding for @hanzo/observe. Makes @hanzo/gui (Tamagui) / React Native apps and Tauri desktop emit the same canonical Events as the web — same semantic hierarchy, same privacy gate, same ONE front door (POST /v1/event via @hanzo/event).

Native has no DOM to walk, so the semantic hierarchy is composed from explicit per-element meta and the surrounding ObserveScope stack — the native equivalent of the web's DOM ancestry, auto-derived from the React tree.

Tamagui / React Native

import { createAnalytics } from '@hanzo/event'
import { ObserveProvider, ObserveScope, useObserve } from '@hanzo/observe-native'

function App() {
  return (
    <ObserveProvider client={createAnalytics({ product: 'app' })}>
      <ObserveScope name="Dashboard">
        <ObserveScope name="UserCard">
          <UserCard />
        </ObserveScope>
      </ObserveScope>
    </ObserveProvider>
  )
}

function UserCard() {
  const o = useObserve()
  return (
    <>
      <Button onPress={o.press('SaveButton', save)} />          {/* Dashboard/UserCard/SaveButton */}
      <Input onChangeText={o.changeText('email', setEmail)} />  {/* value redacted */}
    </>
  )
}

press wraps onPress, changeText wraps onChangeText (RN/Tamagui props) — the interaction is captured, then your handler runs. o.event(name) and o.screen(name) cover custom events and screen views. useEventStream() gives the live rolling window for session playback, same as the web.

Tauri desktop

A Tauri window is a webview, so the DOM lives — bindTauri runs the @hanzo/observe DOM engine to capture the in-webview UI exactly like the web, and forwards Tauri's native window/app events. The /tauri entry is React-free:

import { createAnalytics } from '@hanzo/event'
import { bindTauri } from '@hanzo/observe-native/tauri'

const bridge = bindTauri(createAnalytics({ product: 'desktop' }))
// … later
bridge.stop()

@tauri-apps/api is an optional peer loaded at runtime; calling bindTauri outside a Tauri runtime is safe (the native bridge no-ops, DOM capture still runs in any webview).

Privacy

Identical policy to the web, via the shared @hanzo/observe primitives: input values are withheld by default, sensitive fields (password / email / card / …) are always redacted, and everything is fail-soft. Pass redaction={{ … }} on ObserveProvider (or bindTauri) to tune it.

Same wire, everywhere

A native tap and a web click produce the identical event shape ($click, $el, $path, $component, $value, …) because both go through the one wireProps projection in @hanzo/observe. One vocabulary across web, mobile, and desktop.

License

BSD-3-Clause © Hanzo AI