Files
zeekay 75d32ffea4 observe: a page view reports its engaged time as $pageleave; replay compresses what would not fit
@hanzo/observe 0.1.15 times every page view: active milliseconds (visible,
focused, input in the last 60 s), each watched section's time in view, the
furthest scroll and the share of the page it showed, and the load's web vitals.
It reports in segments, when the page is hidden, unloaded, routed away from or
the engine stops, so the time on a view is the sum of $active_ms over its
$view_id and a phone that never fires pagehide still reports. A hidden or
unloaded page's segment goes at once by beacon; a route change's is filed under
the page left. deliver() is the one delivery every binding makes (React,
Svelte, Tauri).

@hanzo/event 0.3.64: capture() takes the page an event belongs to.

@hanzo/replay 0.1.4 gzips a full snapshot, and any mutation or style rule over
4 KiB, in the cv 2024-10 encoding the insights player decodes. The landing's
snapshot is 1.32 MB raw and was refused by the 512 KiB ingest; it now goes as
314 KB. /pricing, 541 KB raw, goes as 167 KB. The privacy tests read payloads as
the player does, so an absence cannot pass for being compressed.

The observe family names its siblings workspace:^ so a release of one is built
against the other.
2026-10-30 06:51:25 -07:00
..
2026-09-08 23:50:28 -07:00

@hanzo/observe-svelte

Svelte adaptor for @hanzo/observe. Same engine, same semantic capture, same ONE entry point (POST /v1/event via @hanzo/event) — bound to Svelte idioms: a bootstrap, an action, and a store.

Bootstrap

Start capture once, in a root layout, with a @hanzo/event client:

<!-- +layout.svelte -->
<script>
  import { onMount } from 'svelte'
  import { createAnalytics } from '@hanzo/event'
  import { createObserver } from '@hanzo/observe-svelte'

  onMount(() => createObserver(createAnalytics({ product: 'app' })))
</script>

<slot />

Every click, input, navigation, and (opt-in) visibility across the app is now captured, annotated with its semantic hierarchy, and emitted through the client. createObserver is idempotent and SSR-safe.

The observe action

Svelte components have no stable runtime name, so stamp one — the engine then labels every interaction inside the node with it:

<script>
  import { observe } from '@hanzo/observe-svelte'
</script>

<section use:observe={{ name: 'UserCard' }}>
  <button>Save</button>   <!-- captured as UserCard/button[Save] -->
</section>

<div use:observe={{ private: true }}>…</div>   <!-- excluded from capture -->
<div use:observe={{ view: true }}>…</div>       <!-- $view when it scrolls in -->

Session playback

stream is a Svelte-readable store over the live capture stream — a rolling window for a playback timeline:

<script>
  import { stream } from '@hanzo/observe-svelte'
  const events = stream({ limit: 200 })
</script>

<ol>
  {#each $events as e}
    <li>{e.name} → {e.semantic.label}</li>
  {/each}
</ol>

Privacy

Inherited from @hanzo/observe: input values are withheld by default, sensitive fields are always redacted, and data-hz-private (or use:observe={{ private: true }}) excludes a subtree. Everything is fail-soft.

License

MIT © Hanzo AI — see LICENSE.md. HIP-0137 (hanzoai/hips).