mirror of
https://github.com/hanzoai/insights-js.git
synced 2026-11-03 00:53:53 +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.
47 lines
2.0 KiB
TypeScript
47 lines
2.0 KiB
TypeScript
'use client'
|
|
|
|
import { useFeatureFlag, useActiveFeatureFlags } from '@hanzo/insights-next'
|
|
|
|
export default function SSRBootstrapPage() {
|
|
// These values are available immediately on first render - no flicker.
|
|
// The PostHogProvider in layout.tsx has `bootstrapFlags` enabled, which
|
|
// evaluates flags server-side and passes them to the client via bootstrap.
|
|
const activeFlags = useActiveFeatureFlags()
|
|
const exampleFlag = useFeatureFlag('example-flag')
|
|
|
|
return (
|
|
<div>
|
|
<h1 className="text-2xl font-bold mb-2">SSR Bootstrapped Feature Flags</h1>
|
|
<p className="text-gray-600 mb-6">
|
|
This page uses client-side hooks (<code className="bg-gray-100 px-1 rounded">useFeatureFlag</code>
|
|
), but because the layout has <code className="bg-gray-100 px-1 rounded">bootstrapFlags</code> enabled,
|
|
flag values are available on the first render with no flicker.
|
|
</p>
|
|
|
|
<div className="bg-white rounded-lg border border-gray-200 p-6 mb-4">
|
|
<h2 className="font-semibold mb-2">Example Flag</h2>
|
|
<pre className="bg-gray-50 p-3 rounded text-sm overflow-auto">
|
|
{JSON.stringify(exampleFlag, null, 2) ?? 'undefined'}
|
|
</pre>
|
|
</div>
|
|
|
|
<div className="bg-white rounded-lg border border-gray-200 p-6">
|
|
<h2 className="font-semibold mb-2">Active Feature Flags</h2>
|
|
{activeFlags && activeFlags.length > 0 ? (
|
|
<ul className="text-sm space-y-1">
|
|
{activeFlags.map((flag) => (
|
|
<li key={flag} className="font-mono">
|
|
{flag}
|
|
</li>
|
|
))}
|
|
</ul>
|
|
) : (
|
|
<p className="text-sm text-gray-500">
|
|
No active flags. Create some in your PostHog project to see them here.
|
|
</p>
|
|
)}
|
|
</div>
|
|
</div>
|
|
)
|
|
}
|