Jakob Wennberg
d4f82cafc4
Recapt shuts down in four days, taking product analytics and session replay with it. This adds PostHog Cloud EU alongside it; the Recapt removal follows separately so events can be confirmed landing first. Wiring choices that are not the tutorial defaults: - Same-origin reverse proxy (/rl -> eu.i.posthog.com) instead of adding PostHog hosts to the CSP. connect-src 'self' and script-src 'self' already cover it, tracking blockers have no third-party host to match, and the Recapt allowlist entries in next.config.ts get replaced by nothing at all when they go. Needs skipTrailingSlashRedirect, since PostHog sends trailing-slash API requests; verified that trailing-slash URLs on normal routes still resolve 200 rather than 404. - /rl is excluded from the proxy.ts matcher. Middleware runs BEFORE next.config rewrites, so without this updateSession() treats an ingestion POST as an unknown protected path and 307s it to /login. Verified with a control: /zz/flags/ -> 307 /login, /rl/flags/ -> 200 from PostHog. This fails silently otherwise, because asset loads keep working through the rewrite while no events arrive. - persistence: 'memory' so nothing is written to the device and no cookie-consent banner is required. Everything post-login is unaffected: AnalyticsIdentify re-identifies on each dashboard load. - session_recording.maskTextSelector: '*'. PostHog masks inputs but not text by default, and this app renders org numbers (which for an enskild firma ARE the owner's personnummer), customer names and balances as ordinary text. Replays show where a user gets stuck, never what their books say. buildGroupProperties() also refuses to send org_number at all, with a test pinning it. - Error tracking registers through the existing lib/observability sink rather than bypassing it, so every error-level createLogger() line is captured already redacted. instrumentation.ts onRequestError covers what escapes uncaught. Analytics is hosted-only: isAnalyticsEnabled() short-circuits on NEXT_PUBLIC_SELF_HOSTED and no Docker sentinel is added, so self-hosted runs with zero third-party runtime code. Recapt got that outcome only by accident, via a missing sentinel; here it is explicit and tested. vitest.config.ts aliases 'server-only' to a stub: it is a build-time guard whose real entry point always throws, which broke 48 test files the moment a server-only module entered the graph. request-context.ts was already carrying the same latent trap. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
48 lines
1.7 KiB
TypeScript
48 lines
1.7 KiB
TypeScript
import 'server-only'
|
|
import { PostHog } from 'posthog-node'
|
|
import { isAnalyticsEnabled } from './enabled'
|
|
|
|
/**
|
|
* Server-side PostHog client (posthog-node).
|
|
*
|
|
* posthog-js is browser-only, so anything captured from a route handler, a
|
|
* server component or the onRequestError hook goes through here.
|
|
*
|
|
* `flushAt: 1` / `flushInterval: 0` are NOT tuning: Vercel functions are torn
|
|
* down per invocation, and the SDK's default batching would let the process
|
|
* die before the enqueued event is sent. With these set, every capture sends
|
|
* on its own, and callers must still `await flushAnalytics()` before
|
|
* returning or the send races the teardown.
|
|
*
|
|
* Returns null when analytics is off (self-hosted, or no token), so callers
|
|
* degrade to a no-op instead of throwing.
|
|
*/
|
|
let client: PostHog | null = null
|
|
|
|
export function getPostHogServer(): PostHog | null {
|
|
if (!isAnalyticsEnabled()) return null
|
|
if (!client) {
|
|
client = new PostHog(process.env.NEXT_PUBLIC_POSTHOG_PROJECT_TOKEN!, {
|
|
// Server-side traffic is not ad-blocked, so it talks to PostHog
|
|
// directly rather than through the /rl same-origin rewrite (which only
|
|
// exists in the browser's Next.js routing anyway). This is the only
|
|
// reader of NEXT_PUBLIC_POSTHOG_HOST; the EU default keeps it optional.
|
|
host: process.env.NEXT_PUBLIC_POSTHOG_HOST || 'https://eu.i.posthog.com',
|
|
flushAt: 1,
|
|
flushInterval: 0,
|
|
enableExceptionAutocapture: true,
|
|
})
|
|
}
|
|
return client
|
|
}
|
|
|
|
/** Await this before a request handler returns, or the send is dropped. */
|
|
export async function flushAnalytics(): Promise<void> {
|
|
if (!client) return
|
|
try {
|
|
await client.flush()
|
|
} catch {
|
|
// Telemetry must never fail a real request.
|
|
}
|
|
}
|