Files
zooqueen a93e642791 chore: complete posthog->insights rebrand (zero @posthog/* identity)
Decomplect the half-finished fork so the dependency graph has ONE source
with no posthog package identity, living under github.com/hanzoinsights.

LAYER 1 (package identity): rename straggler package.json names —
@posthog/next->@hanzo/insights-next (Next.js SDK; distinct from the existing
@hanzo/insights-nextjs config helper), @posthog/mcp->@hanzo/insights-mcp,
@posthog/plugin-utils->@hanzo/insights-plugin-utils,
@posthog/react-slim->@hanzo/react-slim, @posthog-tooling/release->
@hanzo/insights-tooling-release, and the @posthog/rrweb* family->@hanzo/rrweb*
(matching the already-published @hanzo/rrweb*@0.0.47 + minimumReleaseAgeExclude).
Repoint every repository.url/homepage/bugs to github.com/hanzoinsights/insights-js
and rebrand the PostHog author/description identity to Hanzo AI.

LAYER 2 (cross-package imports): rewrite every internal @posthog/* import to its
@hanzo/insights*|@hanzo/rrweb* equivalent and the bare module specifiers
posthog-js->@hanzo/insights, posthog-node->@hanzo/insights-node, mirrored in
package.json deps + the pnpm-lock importer keys. Result: 0 @posthog/* specifiers
in packages/tooling/examples/playground source.

LAYER 4 (wire protocol) PRESERVED: window.posthog global, ph_* keys,
$-prefixed event names, distinct_id, /decide, /e/, /flags, and the
__PosthogExtensions__ hook are left unchanged — the Insights server expects them.

Also repair pre-existing fork merge damage that blocked compilation (unrelated to
naming; identical to origin/main): restore the @hanzo/insights-core ./process
subpath (spawn-local/utils, re-matching the published artifact), the lost
constructor/var declarations in core + node clients, the mangled
external-scripts-loader, the missing TreeShakeable/isPlainError imports, the
DeviceId enum member, and stale ../posthog-core-stateless module paths. 26/34
turbo build tasks now pass; remaining failures (browser/react-native and their
dependents) are pre-existing fork damage, not rebrand-caused.
2026-06-19 18:44:26 -07:00

59 lines
2.4 KiB
TypeScript

'use client'
import { useState } from 'react'
import { usePostHog } from '@hanzo/insights-next'
export default function CapturePage() {
const posthog = usePostHog()
const [events, setEvents] = useState<string[]>([])
function capture(eventName: string, properties?: Record<string, unknown>) {
posthog.capture(eventName, properties)
setEvents((prev) => [...prev, `${eventName}${properties ? ' ' + JSON.stringify(properties) : ''}`])
}
return (
<div>
<h1 className="text-2xl font-bold mb-2">Event Capture</h1>
<p className="text-gray-600 mb-6">
Capture custom events using <code className="bg-gray-100 px-1 rounded">posthog.capture()</code>. Events
appear in your PostHog project&#39;s activity feed.
</p>
<div className="bg-white rounded-lg border border-gray-200 p-6 mb-4">
<h2 className="font-semibold mb-4">Capture Events</h2>
<div className="flex gap-3 flex-wrap">
<button
onClick={() => capture('button_clicked')}
className="px-4 py-2 bg-gray-900 text-white rounded hover:bg-gray-700"
>
Basic Capture
</button>
<button
onClick={() => capture('button_clicked', { section: 'demo', variant: 'primary' })}
className="px-4 py-2 bg-blue-600 text-white rounded hover:bg-blue-500"
>
With Properties
</button>
</div>
</div>
<div className="bg-white rounded-lg border border-gray-200 p-6">
<h2 className="font-semibold mb-2">Event Log</h2>
<p className="text-sm text-gray-500 mb-3">Events captured this session:</p>
{events.length > 0 ? (
<ul className="space-y-1">
{events.map((event, i) => (
<li key={i} className="text-sm font-mono bg-gray-50 px-3 py-1.5 rounded">
{event}
</li>
))}
</ul>
) : (
<p className="text-sm text-gray-400">No events captured yet. Click a button above.</p>
)}
</div>
</div>
)
}