Curated, product-agnostic snapshot of the post-story-04 tree: demo content deleted, auth-only reference feature, web-next shell, all gates green. Product-specific docs, ADRs 027-029, PRDs/epics/archive, editor library traces, and product naming are curated out; generic template repairs (coverage provider devDeps, root test:coverage script, live lint fixes, root-only release-please) are kept. See TEMPLATE.md for provenance, curation list, and usage. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016j8z4VHjedXDTjEDNg7qHK
1.2 KiB
1.2 KiB
@repo/core-analytics
Optional core package providing a vendor-neutral product analytics interface. Scaffold via pnpm turbo gen core-package analytics.
Structure
src/
analytics.interface.ts # IAnalytics — track, identify, pageView, flush
noop-analytics.ts # NoopAnalytics (default no-op implementation)
index.ts # Barrel export
Design
IAnalytics exposes four methods:
track(event, attributes?)— record a named event with optional attributesidentify(user)— associate subsequent events with a userpageView(path, attributes?)— record a page-view eventflush()— drain any in-flight queued events (returnsPromise<void>)
The interface is vendor-neutral: no third-party analytics SDK is bundled. Feature
packages depend on IAnalytics only; concrete implementations (e.g. a PostHog
or Segment adapter) are wired at DI bind time in bind-production.
NoopAnalytics is the default implementation — all methods are no-ops and
flush() resolves immediately via Promise.resolve(). Use it in dev-seed
bindings and unit tests.
See docs/architecture/agent-first-workflow-and-conformance.md for the
dependency-injection conventions.