mirror of
https://github.com/hanzoai/insights-js.git
synced 2026-10-30 18:34:19 +00:00
zooqueen
a93e642791
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.
@posthog/next App Router Example
A Next.js 15 App Router example demonstrating all features of the @posthog/next package.
Setup
-
Copy the environment template:
cp .env.local.example .env.local -
Add your PostHog API key to
.env.local:NEXT_PUBLIC_POSTHOG_KEY=phc_your_key_here NEXT_PUBLIC_POSTHOG_HOST=https://us.i.posthog.com -
From the monorepo root, export packages as tarballs:
pnpm package:watch -
In a new terminal, install dependencies and start the dev server from this directory:
pnpm install pnpm dev
Demos
| Route | Feature | Description |
|---|---|---|
/auth |
Identity | Log in/out with posthog.identify() and posthog.reset() |
/server-flags |
Server Components | Evaluate feature flags server-side |
/client-hooks |
React Hooks | Use useFeatureFlag and friends |
/ssr-bootstrap |
SSR Bootstrap | Feature flags on first render with no flicker |
/capture |
Event Capture | Capture custom events from client components |
Feature Flags
Create these flags in your PostHog project to see the demos in action:
example-flag-- Used by the Client Hooks and SSR Bootstrap demos. Can be boolean or multivariate.