feat(telemetry): add shared defaults and source maps - #71
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
basekit | 7a7d517 | Commit Preview URL Branch Preview URL |
Sep 20 2026, 08:19 PM |
…hing ras-stack's Changesets policy now targets private packages, so the local override goes. Lint covers the repository root as well, which brings the Vite, Vitest, and Playwright configs under the same rules. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
richardsolomou
changed the title
Identify BaseKit telemetry consistently and upload production source maps through the PostHog build integration.
…-repo-checks-2 # Conflicts: # pnpm-lock.yaml
richardsolomou
changed the title
richardsolomou
marked this pull request as ready for review
September 20, 2026 20:22
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The PostHog conformance test checked ras-stack's defaults without proving that BaseKit's provider was wired correctly. Geometry import boundaries were not enforced, repository policy duplicated shared configuration, and production browser errors lacked service metadata and readable source maps.
Changes
I upgraded to ras-stack v2, enabled the shared geometry boundary and Changesets policy, and expanded linting to the repository root. The telemetry test now exercises the real application entrypoint with telemetry configured and absent.
BaseKit's PostHog provider now reports a stable service name, package version, and build environment, with browser logs, metrics, and source maps enabled. Cloudflare production builds upload source maps through the PostHog Vite integration when the project credentials are configured; the personal API key remains build-only and is not exposed to the browser bundle.
Risk
Low. Geometry behavior is unchanged. Telemetry falls back to the existing disabled state when configuration is absent, and source-map uploads run only in Cloudflare production builds with explicit credentials.
Verification
pnpm checkras-stack@2.0.0Checklist