Quentin/plausible setup#48
Merged
Merged
Conversation
Route metric events to a single analytics sink based on configuration: when a Plausible domain is set, forward an allowlisted subset of goals to Plausible (with identity / high-cardinality props stripped); otherwise fall back to the primary metrics pipeline. On web, Plausible's tracker auto-captures pageviews via the History API. Native Plausible is disabled for now (the package is browser-only). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
- Add EXPO_PUBLIC_ENABLE_{GEOLOCATION,LIVE_EVENTS,APP_CONFIG} flags to
env/common.ts, defaulting true so production is unaffected
- Gate live events, app-config, and geolocation fetches behind their
respective flags (both the query enabled condition and prefetch)
- Fix themes.ts circular dependency: import tokens directly from
#/alf/tokens instead of going through the #/alf barrel, which could
yield undefined during webpack module evaluation
- Set all three flags to false in .env for local dev
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Spotchi
force-pushed
the
quentin/plausible-setup
branch
from
June 10, 2026 17:05
0edb9de to
dd6aa55
Compare
flo-bit
approved these changes
Jun 10, 2026
|
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
2 participants
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.
This pull request introduces a secondary analytics pipeline using Plausible Analytics, forwarding selected events to Plausible on web platforms, while keeping the primary metrics pipeline unchanged if that is not configured. It also adds environment-based feature flags to enable or disable major services (geolocation, live events, and app config) via environment variables.
Analytics Integration:
@plausible-analytics/trackerpackage. On Native platforms Plausible initialization is currently a no-opMetricsClientifEXPO_PUBLIC_PLAUSIBLE_DOMAINis not set, use plausible as event sync otherwiseFlags for services still using Bsky endpoints:
EXPO_PUBLIC_ENABLE_GEOLOCATION,EXPO_PUBLIC_ENABLE_LIVE_EVENTS,EXPO_PUBLIC_ENABLE_APP_CONFIG) to selectively enable or disable geolocation, live events, and app config services at runtime.Currently the underlying endpoints all trigger CORS failures, so this mainly cleans up the console errors and stops sending requests to bluesky servers that aren't the appview.