mirror of
https://github.com/hanzoai/insights-js.git
synced 2026-10-30 18:34:19 +00:00
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.
Example app — @posthog/convex
Exercises every method the component exposes — analytics, local feature flag eval, remote feature flag eval, and AI generation tracing — against a real PostHog project. Useful for verifying changes to the component end-to-end and as a runnable reference for setup.
Running it
From the repository root:
pnpm i
pnpm package # builds the tarball that this app installs
pnpm dev --filter example-convex
In a second terminal:
cd examples/example-convex
npx convex dev
npx convex env set POSTHOG_PROJECT_TOKEN phc_… # project token
npx convex env set POSTHOG_PERSONAL_API_KEY phs_… # optional, enables local eval
npx convex env set POSTHOG_HOST https://us.i.posthog.com # optional, US default
What you'll see
- Sections 01–03 capture analytics events (verify them in your PostHog activity feed).
- Section 04 has two rows of buttons — local-eval methods (query context, reactive) and
remote-eval methods (action context, per-call
/flagsrequest). - Section 05 captures
$ai_generationevents through@posthog/ai, defaulting to OpenTelemetry with manual capture as the alternative. See LLM analytics for Convex. - The right column shows the local evaluation cache state plus a live, reactive view of flag values for the current Distinct ID — change a flag in PostHog and the row flashes when the cron picks it up.