Skip to content

Add a first-class expoRouterIntegration() with auto-registration (#6156) #6189

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
alwx merged 6 commits into from
May 20, 2026

Updated CHANGELOG.md

25475dc
Select commit
Loading
Failed to load commit list.
Merged

Add a first-class expoRouterIntegration() with auto-registration (#6156) #6189

Updated CHANGELOG.md
25475dc
Select commit
Loading
Failed to load commit list.
@sentry/warden / warden: code-review completed May 19, 2026 in 11m 47s

1 issue

code-review: Found 1 issue (1 medium)

Medium

Reliance on private internal expo-router module path may break on version upgrades - `packages/core/src/js/tracing/expoRouterIntegration.ts:90-97`

Accessing expo-router/build/global-state/router-store couples the integration to an undocumented internal module path that can be renamed or restructured in any expo-router release without a semver major bump, silently breaking navigation instrumentation for all users on a new version.

⏱ 11m 31s · 737.8k in / 52.3k out · $1.58

Annotations

Check warning on line 97 in packages/core/src/js/tracing/expoRouterIntegration.ts

See this annotation in the file changed.

@sentry-warden sentry-warden / warden: code-review

Reliance on private internal expo-router module path may break on version upgrades 

Accessing `expo-router/build/global-state/router-store` couples the integration to an undocumented internal module path that can be renamed or restructured in any expo-router release without a semver major bump, silently breaking navigation instrumentation for all users on a new version.
View more details on @sentry/warden